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 2009/01/21 07:20:59 UTC

[jira] Resolved: (JSEC-38) DefaultSecurityManager 'globalSessionTimeout' property

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