after an IRC discussion, I was reminded that you can't set up your twiki to use login names, and allow users to set passwords. There is an assumption in TWikiRegistration
that if you
that you would also set the PasswordManager
to none, use apache auth, and have all user management done somewhere else.
This is one of those places where we need to write out the matrix of options, and work out howto make them all possible.
THUS, this is a 4.2.1 or later issue, and will not be fixed in the 4.2.0 release
for eg, if you use an external auth management system (eg. you're adding twiki to an existing web site) and you want to use TemplateLogin
, you must have PasswordManager
(for templatelogin), but you also need to tell twiki to not write to the htpasswd file, etc.
- 21 Sep 2007
Agree. Both on Sven's assessment and that is is a small fix to defer to next patch 4.2.1
- 21 Sep 2007
Analysis with Sven:
, and ChangePassword
need to be depending on whether TWiki handles changing and creating password.
Only the Password Handler knows this.
The fix will be that these handlers set a context and an IF in the 3 pages can then...
- TWikiRegistration - the password field will only be visible when the context is true
- ResetPassword, and ChangePassword - will have conditional code so that the reset or change password form is only visible if this password handler context is true. Otherwise a generic text will say that setting and resetting of passwords is handled elsewhere. We may even create a setting where an admin can define a URL that these pages point to for resetting and changing passwords.
Target for this is 4.2.3
- 02 Aug 2008
Target is now 4.2.4
The action required is that someone helps finding the best way to introduce a context we can test for - for the password field. Ie let the password handler set a context if it handles passwords so we can test for is to decide if password field and reset/change password are displayed.
I can take care of the topics and the conditional code there as long as someone helps with the context code. If we do not get this closed within a week I will defer it to 5.0.
- 18 Sep 2008
Let's defer this to after 4.3.0 release.
- 02 Feb 2009
Reprioritizing this to normal. See TWiki:Codev/HelsinkiReleaseMeeting2010x04x26
- 26 Apr 2010
I am setting this to "no action required" - it had no action for a number of years. Please open a new item if you want to address this.