Question

I am upgrading the ApplicationAuthenticationAddOn, and want to make this configurable in TWIKI.cfg instead of editing script files with constants. BUT I need to generate html with these parms for the logon form. Its not clear what where variables come from. I really want all the configuration in TWIKI.cfg, not TWikiPreferences. When I set AuthenticationStyle=ApplicationLDAP I want to handle all that in the standard scripts.

SO, when does a variable go in TWiki.cfg vs TwikiPreferences, and I believe I can access some from Perl and some from HTML but NOT all from either.. Is this correct?

thanks

Environment

-- SamDetweiler - 06 May 2005

Answer

While I haven't had an answer to these design questions, I have solved my logon problem with the AuthPagePlugin instead. This does just about everything I was looking for..

Still have the '@' removed from my users id on edits and historys tho.. would like to solve that one too..

-- SamDetweiler - 07 May 2005

The @ is an illegal character. because it is perl syntax and could potentially be used to scompromise security. If you want to take that risk, you can edit the name filter in TWiki.cfg. i think that should work.

On architecture; there is no clean architecture for adding preferences to TWiki.cfg in Cairo, and I really couldn't recommend it. DakarRelease has a re-architected approach that lets you add abitrary variables to a global config hash, and also maintains site-local config files, which is what you want I think.

-- CrawfordCurrie - 30 Jun 2005