Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
None
Description
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.
Attachments
Issue Links
- is duplicated by
-
JENKINS-11505 Single-sign-on isn't working correctly in the Crowd 2 plugin
-
- Resolved
-
-
JENKINS-11506 Single-sign-on isn't working correctly in the Crowd 2 plugin
-
- Resolved
-
- relates to
-
JENKINS-52306 Improve SSO logout
-
- In Progress
-
Activity
Field | Original Value | New Value |
---|---|---|
Status | Open [ 1 ] | In Progress [ 3 ] |
Resolution | Fixed [ 1 ] | |
Status | In Progress [ 3 ] | Resolved [ 5 ] |
Link |
This issue is duplicated by |
Link |
This issue is duplicated by |
Status | Resolved [ 5 ] | Closed [ 6 ] |
Workflow | JNJira [ 141734 ] | JNJira + In-Review [ 205425 ] |
Link | This issue relates to JENKINS-52306 [ JENKINS-52306 ] |
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.