I have configured my JIRA instance to use SSO, and it is working if I navigate to a secure URL (https://192.168.16.121/browse/<ProjectKey>).
However, if I navigate to the root URL of the server (https://192.168.16.121/), I see the following set of redirections:
https://192.168.16.121/ redirects to:
https://192.168.16.121/secure/MyJiraHome.jspa redirects to:
Of course login.jsp is the login screen.
In seraph-config.xml both login.url and link.login.url are set to the same URL.
How can I make either the root or MyJiraHome.jspa use correct SSO URL?
I don't know what you mean by "not been set properly". If you mean it has not been authenticated, or doesn't yet exist, you are right.
The first rediect makes sense (Take this person to the default landing page). The second (This person needs to be authenticated so I can provide correctly authorized content) makes sense conceptually, but the destination seems broken.
The docs in seraph-config.xml indicate that the login.url init-param contains the url that should be used for login. It does, and it works for content that is not MyJiraHome.jspa (browsing a project).
Short of hacking up login.jsp to initiate an SSO handshake I don't see a way of fixing that.
link.login.url is working correctly. If, from the login.jsp UI, I click the login link in the top right corner of the screen, I am directed to the SSO system, authenticated, and redirected to my JIRA Dashboard.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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