Jira Home Screen Error (Login Screen Missing at System Dashboard)

[Marcelo Viana de Siqueira]

Hi folks!

After upgrading Jira Data Center from version 9.12.15 to 10.3.2 (LTS), it was identified that the authentication gadget no longer appears on the home screen (/secure/Dashboard.jspa).

It´s the same problem reported here: https://community.atlassian.com/t5/Jira-questions/Why-is-there-no-login-in-my-JIRA-System-Dashboard/qaq-p/2912093

Has anyone here updated to version 10.3.x without experiencing this issue? If the issue occurred, were you able to find a solution?

[Shawn Doyle - ReleaseTEAM · Accepted solution]

Hi @Marcelo Viana de Siqueira 

I wonder if you are having issues due to this  

Jira 10.2: New login experience with two-step verification

To improve the security of the Jira login experience, we’ve added a second authentication layer. If you experience any issues with the new login process, you can switch to the legacy login experience by setting the JVM system property atlassian.authentication.legacy.mode to true.

https://confluence.atlassian.com/jirasoftware/jira-software-10-3-x-upgrade-notes-1472791008.html

I would attempt to turn the legacy mode to true and see if that brings back your login.  Then push Atlassian for a fix or workaround to the new login experience.

[Marcelo Viana de Siqueira]

Hi @Shawn Doyle - ReleaseTEAM , thanks for your input!

The issue has been resolved.

Solution: Insert the variable -Datlassian.authentication.legacy.mode=true in the <jira_dir_install>/bin/setenv.sh file, inside the JVM_SUPPORT_RECOMMENDED_ARGS parameter.

Thanks!

[Meriem Amdouni]

Hi @Marcelo Viana de Siqueira , that was helpful, thank you.

[Jukka Pirinen]

Yes setting legacy mode works, but the two-factor authentication not working anymore.

[Jukka Pirinen]

As the jira instance and the system dashboard I have the problem is not public, I enabled following site wide dark feature:

public.access.disabled

Now it redirects to login automatically.

[ivv Jira Admin]

Has anyone seen a ticket regarding a real fix or explanation to this problem?
We're having a similar issue, but the problem only exists in our test environments and NOT in production, although we seem to have the same version AND config for both servers, which is legacy.mode = false.

legacy.mode = true fixes the missing login box for our test environments but in production it's false and the login works.