|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
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.