[
https://issues.apache.org/jira/browse/SHIRO-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15733226#comment-15733226
]
Brian Demers commented on SHIRO-604:
------------------------------------
Thanks for the report [~sreenivash09]!
It _should_ be set from
[here|https://github.com/apache/shiro/blob/ef5450b9f4be74ee930401115394823b9e1fc3e6/core/src/main/java/org/apache/shiro/session/mgt/AbstractNativeSessionManager.java#L100]:
https://github.com/apache/shiro/blob/ef5450b9f4be74ee930401115394823b9e1fc3e6/core/src/main/java/org/apache/shiro/session/mgt/AbstractNativeSessionManager.java#L100]
Can you create a simple reproduce case or test?
> 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)
