You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shiro.apache.org by "sreenivas Harshith (JIRA)" <ji...@apache.org> on 2016/12/08 19:03:58 UTC
[jira] [Commented] (SHIRO-604)
securityManager.sessionManager.globalSessionTimeout value set in shiro.ini
is ignored
[ https://issues.apache.org/jira/browse/SHIRO-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15733104#comment-15733104 ]
sreenivas Harshith commented on SHIRO-604:
------------------------------------------
I debugged through the source and found that when SimpleSession is created its defaulted in its constructor
public SimpleSession() {
this.timeout = DefaultSessionManager.DEFAULT_GLOBAL_SESSION_TIMEOUT; //TODO - remove concrete reference to DefaultSessionManager
this.startTimestamp = new Date();
this.lastAccessTime = this.startTimestamp;
}
> securityManager.sessionManager.globalSessionTimeout value set in shiro.ini is ignored
> -------------------------------------------------------------------------------------
>
> Key: SHIRO-604
> URL: https://issues.apache.org/jira/browse/SHIRO-604
> Project: Shiro
> Issue Type: Bug
> Components: Session Management
> Affects Versions: 1.3.2
> Reporter: sreenivas Harshith
> Labels: customSessionDAO, customSessionvalue, globalSessionTimeout, session
>
> securityManager.sessionManager.globalSessionTimeout value is ignored when using the native shiro DefaultWebSessionManager and custom SessionDAO. Its defaulted to 1800000
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)