Closed GoogleCodeExporter closed 8 years ago
In the second patch, you have several calls like
«self::updateSessionCookies». Since this function isn't static, it should be
$this->updateSessionCookies instead.
In the second patch, I think setRememberMeExpire() should also update the
session cookie lifetime. That would make the third patch less dependant on the
internals of the session object.
In the third patch, you are also calling setSessionDuration(). That function
shouldn't be used any more. It is only present because of
backwardscompatibility. (I guess I should mark it as deprecated somehow).
Instead, you should update the 'Expire' value for the authentication source the
current authproc filter is using as base data. The problem is identifying that
authentication source. It looks like you will have to add it to the processing
state from the IdP.
For the third patch, you should probably include a bit of documentation
somewhere. Actually, you may want to write a document showing how to take
advantage of this entire feature :)
Btw.: If you aren't using it to bould your patch series already, you should
have a look at «git format-patch».
Original comment by olavmrk@gmail.com
on 12 Sep 2013 at 9:29
Here are updated patches.
1. Updated for trunk.
2. Updated updateSessionCookies() and added setAuthorityExpire().
3. Updated for new updateSessionCookies() and setAuthorityExpire().
We are using somehow specific workflow for this project, so we are not using
git format-patch. Thanks for the tip.
Original comment by comel...@gmail.com
on 12 Sep 2013 at 3:43
Attachments:
Only a couple of remarks against the last patch:
- You refer to sspmod_common_Util::getGlobalConfig() , but that one doesn't
exist.
- Maybe this patch is more of an example? In that case it probably belongs in
exampleauth?
Other than that, these patches look good.
Original comment by olavmrk@gmail.com
on 13 Sep 2013 at 10:55
Authentication processor was at first in custom module which is modified for
patch 3 and sspmod_common_Util::getGlobalConfig is leftover. It's fixed now.
Patches are committed as r3275, r3276 and r3277. Thanks!
Original comment by comel...@gmail.com
on 13 Sep 2013 at 11:16
Original issue reported on code.google.com by
comel...@gmail.com
on 10 Sep 2013 at 12:40Attachments: