You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shiro.apache.org by "Les Hazlewood (JIRA)" <ji...@apache.org> on 2008/12/16 15:30:46 UTC
[jira] Created: (JSEC-38) DefaultSecurityManager
'globalSessionTimeout' property
DefaultSecurityManager 'globalSessionTimeout' property
------------------------------------------------------
Key: JSEC-38
URL: https://issues.apache.org/jira/browse/JSEC-38
Project: JSecurity
Issue Type: Improvement
Components: Session Management
Affects Versions: 1.0
Reporter: Les Hazlewood
Fix For: 1.0
A 'globalSessionTimeout' property should be accessible on the DefaultSecurityManager implementation so that its setting could propagate down to the DefaultSessionManager implementation. This is a convenience feature so the end-user doesn't have to configure a SessionManager implementation and then inject it into the SecurityManager implementation. Instead, they can set a single property:
sessionManager.globalSessionTimeout = blah
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Moved: (KI-64) DefaultSecurityManager 'globalSessionTimeout'
property
Posted by "Alan Cabrera (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KI-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alan Cabrera moved JSEC-38 to KI-64:
------------------------------------
Fix Version/s: (was: 1.0)
Component/s: (was: Session Management)
Affects Version/s: (was: 1.0)
Key: KI-64 (was: JSEC-38)
Project: Ki (was: JSecurity)
> DefaultSecurityManager 'globalSessionTimeout' property
> ------------------------------------------------------
>
> Key: KI-64
> URL: https://issues.apache.org/jira/browse/KI-64
> Project: Ki
> Issue Type: Improvement
> Reporter: Les Hazlewood
> Assignee: Les Hazlewood
>
> A 'globalSessionTimeout' property should be accessible on the DefaultSecurityManager implementation so that its setting could propagate down to the DefaultSessionManager implementation. This is a convenience feature so the end-user doesn't have to configure a SessionManager implementation and then inject it into the SecurityManager implementation. Instead, they can set a single property:
> sessionManager.globalSessionTimeout = blah
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JSEC-38) DefaultSecurityManager
'globalSessionTimeout' property
Posted by "Les Hazlewood (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JSEC-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Les Hazlewood resolved JSEC-38.
-------------------------------
Resolution: Fixed
Assignee: Les Hazlewood
Implementation complete with passthrough methods:
http://svn.apache.org/viewvc?rev=736235&view=rev
> DefaultSecurityManager 'globalSessionTimeout' property
> ------------------------------------------------------
>
> Key: JSEC-38
> URL: https://issues.apache.org/jira/browse/JSEC-38
> Project: JSecurity
> Issue Type: Improvement
> Components: Session Management
> Affects Versions: 1.0
> Reporter: Les Hazlewood
> Assignee: Les Hazlewood
> Fix For: 1.0
>
>
> A 'globalSessionTimeout' property should be accessible on the DefaultSecurityManager implementation so that its setting could propagate down to the DefaultSessionManager implementation. This is a convenience feature so the end-user doesn't have to configure a SessionManager implementation and then inject it into the SecurityManager implementation. Instead, they can set a single property:
> sessionManager.globalSessionTimeout = blah
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.