You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shiro.apache.org by "Alan Cabrera (JIRA)" <ji...@apache.org> on 2009/03/06 14:59:57 UTC

[jira] Moved: (KI-64) DefaultSecurityManager 'globalSessionTimeout' property

     [ 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.