We have a client who upgraded JIRA from 7.1.9 to 7.3.6 and it appears that OKTA SSO is not working the same way it worked before. As soon as you click on JIRA URL from OKTA you get redirected to JIRA Dashboard login page but if you click refresh or just click on JIRA logo it logs you in. Did you see the similar behaviour with latest JIRA and does your OKTA plugin supports it? The current client plugin version is 2.0.2 I thought that we can try to upgrade to 2.0.4 but I need an support matrix for your versions or an evidence that the latest version indeed fixes the issue.
Our teams developed the Jira Authenticator 3.0 which is in Beta currently, especially to support 7.x versions of JIRA. The current supported (tested) versions for our Authenticator are : JIRA Software7.0.10, 7.1.4, 7.2.8, 7.3.3, 7.3.4 JIRA ServiceDesk3.0.10, 3.1.4, 3.2.8, 3.4.0, 3.4.1 JIRA Core7.0.10, 7.1.4, 7.2.8, 7.3.3, 7.3.4
There is an issue though with SP-Initiated SSO when logging in from the Dashboard of the page as it is considered a common access page and it doesn't automatically sign-in unless the user clicks the "Sign In" button.
For more information about this flag, the functionality and how to have access to the 3.0 version of the Authenticator you can also contact Okta Support and open a new ticket.
Ovidiu Pirvu Technical Support Engineer Okta Global Customer Care
Were you able to get Jira Authenticator 3.0? and did it help? We are attempting to implement the below: Jira On-Premise: 7.3.6 Plugin: okta-jira-2.0.5 But, Jira url won't come up after configuration, and it looks like it is getting stuck trying authenticate "anonymous" for a "health-check". Have you seen this before or in testing?
I have exactly the same issue as Vladimir. Can you advise whether it would be possible to obtain the JIRA Authenticator 3.0 Beta so that I can test it on our upgraded JIRA development system. If not, when do you expect the software to be available for release?
We have installed the latest JIRA Authenticator 3.0 and it fixed the issue for the client. Also the plugins must be obtained by OKTA admin as they have access to the OKTA download section through admin interface.