I'm running into an issue logging into JIRA. I have just completed upgrading from version 4.0.x to version 5.x (along with upgrading Crowd from 1.6 to 2.4—an ordeal, I assure you).
We use the JIRA WAR version on our own servers. The servlet context we use on Tomcat is /jira/. We can log in using the top-right login link (taking us to the login page) however using the login widget doesn't work: it processes the login fine, but redirects to /jira without the trailing slash. Because of how our servers are configured, this does not map to the /jira/ context and the user gets a 404. Adding the slash to the end of the URI fixes it.
Any idea how to make the login widget redirect to the context with the trailing slash?
Yeah, so I had a support request with this same issue from two and a half years ago :)
The workaround for us was to have two entries in `uriworkermap.properties` for the IIS-Tomcat connector.
This seems to work until JIRA allows base-urls with a trailing slash, or fixes the login widget to add the trailing slash (properly representing the servlet context) properly.
Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot