| <<O>> Difference Topic TWikiLoginManagerDotPm (5 - 2013-10-14 - TWikiContributor) |
| <<O>> Difference Topic TWikiLoginManagerDotPm (4 - 2011-08-21 - TWikiContributor) |
| Line: 192 to 192 | ||||||||
|---|---|---|---|---|---|---|---|---|
ObjectMethod setSessionValue ($name,$value)Set the value of a session variable. | ||||||||
| Changed: | ||||||||
| < < | We do not allow setting of AUTHUSER. | |||||||
| > > | We do not allow setting of AUTHUSER and SESSION_REQUEST_NUMBER. | |||||||
| <<O>> Difference Topic TWikiLoginManagerDotPm (3 - 2011-04-12 - TWikiContributor) |
| Line: 20 to 20 | ||||||||
|---|---|---|---|---|---|---|---|---|
| Here's an overview of how it works: | ||||||||
| Changed: | ||||||||
| < < | Early in TWiki::new, the login manager is created. The creation of the login manager does two things:
| |||||||
| > > | Early in TWiki::new, the login manager is created. The creation of the login
manager does two things:
| |||||||
| Slightly later in TWiki::new, loginManager->loadSession is called. | ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
| ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
| Changed: | ||||||||
| < < | Later again in TWiki::new, plugins are given a chance to override the username found from the loginManager. | |||||||
| > > | Later again in TWiki::new, plugins are given a chance to override the username found from the loginManager. | |||||||
| Changed: | ||||||||
| < < | The last step in TWiki::new is to find the user, using whatever user mapping manager is in place. | |||||||
| > > | The last step in TWiki::new is to find the user, using whatever user mapping manager is in place. | |||||||
ObjectData | ||||||||
| <<O>> Difference Topic TWikiLoginManagerDotPm (2 - 2009-09-02 - TWikiContributor) |
| Line: 273 to 273 | ||||||||
|---|---|---|---|---|---|---|---|---|
| Internal use only TODO: what does it do? | ||||||||
| Added: | ||||||||
| > > | sub createCryptToken ( $session )-> $token Takes the input as session and returns the MD5 hash string. This subroutine is responsible for updating the token database The tokens solve the CSRF issue sub cleanCryptTokens($session, $token) This subroutine takes care of cleaning used tokens Usually called from token verification subroutines. sub addCryptTokeninForm ( )-> returns the form with "crypttoken" html input hidden field If TWiki Application developer has added "crypttoken" then the current subroutine returns the form without performing any parsing. If the form with method - POST do not have any "crypttoken", this subroutine adds the token. | |||||||
| <<O>> Difference Topic TWikiLoginManagerDotPm (1 - 2008-01-22 - TWikiContributor) |
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
| Added: | ||||||||
| > > | Package
The package is also a Factory for login managers and also the base class
for all login managers.
On it's own, an object of this class is used when you specify 'none' in
the security setup section of
configure. When it is used,
logins are not supported. If you want to authenticate users then you should
consider TemplateLogin or ApacheLogin, which are subclasses of this class.
If you are building a new login manager, then you should write a new subclass
of this class, implementing the methods marked as VIRTUAL. There are already
examples in the | |||||||