It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

JIRA ignores login.url when going to root URL

James Higgins Oct 20, 2013

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:

https://192.168.16.121/login.jsp?os_destination=%2Fsecure%2FDashboard.jspa

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?

3 answers

0 votes
Timothy Chin Community Leader Oct 21, 2013

If you get this redirection, it means your session has not been set properly. That would be the correct assessment of your problem right?

James Higgins Oct 22, 2013

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.

0 votes
James Higgins Dec 03, 2013

I'm currently working this with Atlassian support. There is some indications that this is because a dashboard widget on the default dashboard for unauthenticated users. I will keep this updated as I can.

0 votes
Marko Tikkanen Apr 06, 2014

Hi James, did you get any answers or solutions from the Atlassian support for this problem? I'm experiencing the same problem.

Suggest an answer

Log in or Sign up to answer
This widget could not be displayed.
This widget could not be displayed.
Community showcase
Published in Next-gen

Introducing subtasks for breaking down work in next-gen projects

Teams break work down in order to help simplify complex tasks. This is often done iteratively, with tasks being broken down into smaller tasks and so on until the work is accurately captured in well-...

7,396 views 23 35
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you