You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Fresh install of 3.3, but with a server.xml imported from 2.7.2 during the setup.
Setup on default ports. Accessed via reverse proxy in httpd. After import, updated {INSTALL_DIR}/apache-tomcat/conf/server.xml to add proxyPort, proxyName, and scheme.
I am able to login when accessed via IP address, however when accessed via the configured Base URL the login returns to the login page without an error. Browser Network indicates a 302 from j_security_check, but there is no error in the logs. Sometimes (usually before the 'Initiating Jersey' message appears in the log) there is an XSRF failure error.
When logging in through the IP address, various pages will result in an XSRF error in the logs:
2018-12-05 11:06:37,298 http-nio-8095-exec-8 WARN [common.security.jersey.XsrfResourceFilter] Additional XSRF checks failed for request: https://<url>/crowd/rest/webResources/1.0/resources , origin: https://<ip> , referrer: https://<ip>/crowd/console/secure/admin/general.action , credentials in request: true , allowed via CORS: false
The login loop was a result of cache/cookies as described in this KB article
XSRF is resolved when using the url instead of ip address.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.