Sponsored by
Hosted by
Differences
This shows you the differences between two versions of the page.
|
documentation:1.3:upgrade [2012/06/17 15:11] 127.0.0.1 external edit |
documentation:1.3:upgrade [2012/06/18 12:27] (current) coudot |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Upgrade from 1.1 to 1.2 ====== | + | ====== Upgrade from 1.2 to 1.3 ====== |
| <note>If you are using packages, they should have done the upgrade process for you, but you can check here that all is in order.</note> | <note>If you are using packages, they should have done the upgrade process for you, but you can check here that all is in order.</note> | ||
| Line 7: | Line 7: | ||
| * [[:documentation:1.0:upgrade|Upgrade to 1.0]] | * [[:documentation:1.0:upgrade|Upgrade to 1.0]] | ||
| * [[:documentation:1.1:upgrade|Upgrade to 1.1]] | * [[:documentation:1.1:upgrade|Upgrade to 1.1]] | ||
| + | * [[:documentation:1.2:upgrade|Upgrade to 1.2]] | ||
| </note> | </note> | ||
| - | |||
| - | ===== SSL authentication backend ===== | ||
| - | |||
| - | The [[authssl|SSL authentication backend]] behavior has changed: | ||
| - | * Before, when SSL authentication failed, an option could be set to fail back to [[authldap|LDAP authentication backend]]. | ||
| - | * Now, to keep this behavior, you have to use [[authssl|SSL]] and [[authldap|LDAP]] chaining in a [[authmulti|Multi]] configuration: | ||
| - | <code> | ||
| - | Multi SSL;LDAP | ||
| - | </code> | ||
| - | |||
| - | ===== Opening conditions ===== | ||
| - | |||
| - | In LemonLDAP::NG 1.1, you could configure a condition that will be evaluated to allow the sesson creation. | ||
| - | |||
| - | Now, you can define as many conditions as you want. See the [[sessions|sessions configuration page]] to know how. | ||
| - | |||
| - | If you had defined a condition in LemonLDAP::NG 1.1, you are encouraged to redefine it in the new format. | ||
| - | |||
| - | ===== Login history ===== | ||
| - | |||
| - | The [[loginhistory|login history]] is a new feature enabled by default. To turn it off, go in Manager and set 0 in Advanced Parameters > Login History > Activation. | ||
| - | |||
| - | ===== Unprotect rule ===== | ||
| - | |||
| - | The ''unprotect'' rule in Manager now deletes headers forged by an unauthenticated user, but still send headers for authenticated ones. To skip headers for both kind of users, use the ''skip'' rule. | ||
| - | |||
| - | ===== Custom authentication module ===== | ||
| - | |||
| - | If you wrote custom authentication module, you have to add a new method called ''getDisplayType''. This method should return one of these values: | ||
| - | * **standardform**: login/password form | ||
| - | * **openidform**: OpenID login form | ||
| - | * **yubikeyform**: Yubikey login form | ||
| - | * **logo**: no form (used for external authentication methods) | ||
| - | |||
| - | For example: | ||
| - | <file perl> | ||
| - | ## @method string getDisplayType | ||
| - | # @return display type | ||
| - | sub getDisplayType { | ||
| - | return "logo"; | ||
| - | } | ||
| - | </file> | ||
