[
https://issues.apache.org/jira/browse/SHIRO-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dewan Mohammad Moksedul Alam updated SHIRO-446:
-----------------------------------------------
Attachment: shiroAD.conf
exception.txt
I am attaching the configuration file (shiroAD.conf) and the log
(exception.txt).
>From the log it is apparent that at some point of login, it tries to determine
>the hostname and eventually tries to consult with the previous session causing
>this exception as it is already expired and removed from the data source.
I have another scenario, if I set the host from the authentication token, for
example,
token = new UsernamePasswordToken("user", "pass", "host");
SecurityUtils.getSubject().login(token).
Then, the same thing happens at a different place. For this case while merging
principals.
This should not be a usual behaviour.
> Login/logout throws UnknownSessionException for a user whose previous session
> is expired
> ----------------------------------------------------------------------------------------
>
> Key: SHIRO-446
> URL: https://issues.apache.org/jira/browse/SHIRO-446
> Project: Shiro
> Issue Type: Bug
> Components: Authentication (log-in)
> Affects Versions: 1.2.1, 1.2.2
> Reporter: Dewan Mohammad Moksedul Alam
> Attachments: exception.txt, shiroAD.conf
>
>
> After a user session is expired logout attempt is causing an
> UnknownSessionException. This is happening even for every subsequent login
> attempt for the same user. The user cannot be able to login again untill the
> server is restarted.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
