dani/lemonldap-ng
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update debian/NEWS

Browse Source
This commit is contained in:
Xavier Guimard 2016-02-13 18:21:12 +00:00
parent 8d0f4caadf
commit b43cedd47c
1 changed files with 13 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
debian/NEWS vendored
View File

@ -1,5 +1,7 @@
lemonldap-ng (1.9.0-1) unstable; urgency=low lemonldap-ng (1.9.0-1) unstable; urgency=low
1) Configuration and sessions storage
From now, Lemonldap::NG uses JSON serialization to store configuration and From now, Lemonldap::NG uses JSON serialization to store configuration and
sessions instead of Storable::nfreeze Perl function. This permits one to have sessions instead of Storable::nfreeze Perl function. This permits one to have
heterogenous servers connected to the same LLNG organization (32/64 bits or heterogenous servers connected to the same LLNG organization (32/64 bits or
@ -10,6 +12,8 @@ lemonldap-ng (1.9.0-1) unstable; urgency=low
updating an existing session. You can force LemonLDAP::NG to keep the old updating an existing session. You can force LemonLDAP::NG to keep the old
serialization method by setting useStorable to 1 in sessions backend serialization method by setting useStorable to 1 in sessions backend
options if you have some custom hooks. options if you have some custom hooks.
Note that this behaviour only affects modules Apache::Session::File, SQL
database and Apache::Session::LDAP
If you have more than one server and don't want to stop the SSO service, start If you have more than one server and don't want to stop the SSO service, start
upgrading in the following order: upgrading in the following order:
@ -18,6 +22,8 @@ lemonldap-ng (1.9.0-1) unstable; urgency=low
user or client IP and if users use the menu); user or client IP and if users use the menu);
* manager server * manager server
2) Manage Ajax requests when sessions expires
To request for authentication, handlers sent a 302 HTTP code even if request To request for authentication, handlers sent a 302 HTTP code even if request
was an Ajax one. From now, after redirection, portal will send a 401 code was an Ajax one. From now, after redirection, portal will send a 401 code
with a WWW-Authenticate header containing "SSO portal-URL". This is a little with a WWW-Authenticate header containing "SSO portal-URL". This is a little
@ -25,6 +31,8 @@ lemonldap-ng (1.9.0-1) unstable; urgency=low
If you want to keep old behaviour, set noAjaxHook to 1 (in General Parameters If you want to keep old behaviour, set noAjaxHook to 1 (in General Parameters
-> Advanced -> Handler redirections -> Keep redirections for Ajax). -> Advanced -> Handler redirections -> Keep redirections for Ajax).
3) New "Multi" authentication scheme
The Multi backend configuration has changed. Now the stacks are defined in The Multi backend configuration has changed. Now the stacks are defined in
separate attributes: separate attributes:
* multiAuthStack * multiAuthStack
@ -42,6 +50,11 @@ lemonldap-ng (1.9.0-1) unstable; urgency=low
multiAuthStack = LDAP;DBI multiAuthStack = LDAP;DBI
multiUserDBStack = LDAP;DBI multiUserDBStack = LDAP;DBI
4) Form replay
Management of form replay has been rewritten. If you uses this experimental
feature, you must edit your configuration and rewrite it.
-- Xavier Guimard <x.guimard@free.fr> Thu, 21 Jan 2016 17:13:07 +0100 -- Xavier Guimard <x.guimard@free.fr> Thu, 21 Jan 2016 17:13:07 +0100
lemonldap-ng (1.4.6-1) unstable; urgency=medium lemonldap-ng (1.4.6-1) unstable; urgency=medium