[JIRA] [crowd2] (JENKINS-22775) Crowd2 seems to destroy user session when using SSO
Kanstantsin Shautsou assigned JENKINS-22775 to Kanstantsin Shautsou Crowd2 seems to destroy user session when using SSO Change By: Kanstantsin Shautsou (18/Aug/14 4:59 PM) Assignee: ThorstenHeit KanstantsinShautsou 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [crowd2] (JENKINS-22775) Crowd2 seems to destroy user session when using SSO
Kanstantsin Shautsou commented on JENKINS-22775 Crowd2 seems to destroy user session when using SSO Does this comment solves issue? Why plugin and jenkins version is not specified? 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [crowd2] (JENKINS-22775) Crowd2 seems to destroy user session when using SSO
jamus jegier commented on JENKINS-22775 Crowd2 seems to destroy user session when using SSO We had exactly the same issue as this; trying to use Jenkins would destroy the session and start a new one. We had a configuration where all the Atlassian services were behind an apache reverse proxy via mod_proxy, and Jenkins was running on another server, not behind a reverse proxy. We did not configure trusted proxies, so all the Atlassian services were using the loopback address (0:0:0:0:0:0:0:1) to validate the session instead of the client IP address, while Jenkins was using the client IP to validate the session. Once we added 127.0.0.1 and 0:0:0:0:0:0:0:1 to the trusted proxies list in Crowd, we no longer saw this issue. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
