Why do Jira logins sometimes fail?

I have a number of tabs in my web browser (Firefox) which I use for quick reference.

When I start up Firefox in the morning:

  • some of these tabs show whatever they were showing the last time I had Firefox open,
  • some show our normal (JA-SIG Central Authentication Service 3.3.1) Jira login page,
  • others show what looks like a standard Jira login page (this only seems to happen on my agile planning board tab).

If I try to use any page which appears as it did before then I may get shunted to a normal login page (depending on where I were).

If I try to login on a tab which appears as our normal login page (using the saved details filled in by Firefox), then it just shows the login page again having blanked the user and password fields. If I refresh the page before pressing the login button however, then it logs in as expected and returns yuo to the page you were on before.

The standard Jira login page just errors when you try to log in, but if you log in in another window refresh and repost the data then it gets you back to where you were.

This all seems very counterintuitive and is a lot to remember, is it expected behaviour or does our Jira instance have configuration issues? Why does refreshing the page before trying to log in make a difference?

Some additional information:

  • The pages which appear to reload ok on startup appear to be those which don't require any authentication permissions anyway.
  • My dashboard tab
    • http://jira.XXX.uk/secure/Dashboard.jspa reloads as
    • https://auth.XXX.uk/cas/login?service=http%3A%2F%2Fjira.XXX.uk%2Fsecure%2FDashboard.jspa which looks like our normal login screen.
  • My RapidBoard tab
    • http://jira.XXX.uk/secure/RapidBoard.jspa?rapidView=43&view=planning&quickFilter=85 reloads as
    • http://jira.XXX.uk/login.jsp?os_destination=%2Fsecure%2FRapidBoard.jspa%3FrapidView%3D43%26view%3Ddetail%26selectedIssue%3DMTGDA-26%26quickFilter%3D85 which looks like it might be a standard Jira login page.

This looks to me like RapidBoard is redirectling to a standard login page, while Dashboard is redirecting to the local organisation single sign-on.

If it makes any difference, we are on GreenHopper (v6.1.1) & JIRA (v5.0#713-sha1:aec58e2).

1 answer

0 votes
Renjith Pillai Community Champion Jan 08, 2013
This does not look normal. What happens when the login fails in the JIRA logs?

As a user, can I get access to the JIRA logs? or will I have to contact our admin?

You will need to contact the admin for the logs

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

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 ...

3,121 views 13 19
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot