[
https://issues.jenkins-ci.org/browse/JENKINS-11507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thorsten Heit resolved JENKINS-11507.
-------------------------------------
Resolution: Fixed
The problem was that the security realm specified a session validation interval that was set to non-zero value. If you logout from another application, your Jenkins session still remained valid for a couple of minutes.
Additionally some minor improvements were added to the servlet filter.
> Single-sign-on isn't working correctly in the Crowd 2 plugin
> ------------------------------------------------------------
>
> Key: JENKINS-11507
> URL:
https://issues.jenkins-ci.org/browse/JENKINS-11507> Project: Jenkins
> Issue Type: Bug
> Components: crowd2
> Reporter: Thorsten Heit
> Assignee: Thorsten Heit
> Priority: Critical
>
> You are logged in in Jenkins and another application, say, B, that authenticates against a remote Crowd server and uses single-sign-on.
> When you logout from B, your Jenkins session isn't invalidated, i.e. you remain logged in in Jenkins.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
Locked
_0.png)
