<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
System Status
Announcements
Announcements
Search
Search
Select Language
Knowledge Base
Knowledge Articles
Support Videos ↗
Documentation
Product Documentation ↗
Developer Documentation ↗
Product Release Notes ↗
Community
Events & Webinars
Okta Ideas ↗
Resources
Product Hub
Customer Success Hub
Product Release Update
Learning
Okta Learning ↗
Get Support
Open a Case
HomeCommunityForum
0D50Z00008G7VazSAFOkta Classic EngineOkta Integration NetworkAnswered2024-03-25T21:24:49.000Z2018-08-08T18:58:51.000Z2018-08-09T17:55:32.000Z

er961 (er961) asked a question.

Edited by varun.kavoori1.5210444522562532E12 September 5, 2018 at 1:20 AM
Redirect post-login serves false error page
I am configuring Okta with Jira on-prem v7.3.6 and I am getting strange behavior. Once a user logs in via Okta they are redirected to the Jira login page, giving the impression that they are not authenticated.  
  1. Go to http://jira.domain.local:8080
  2. Browser redirects to http://domain.oktapreview.com
  3. User logs in to Okta (successfully)
  4. Broswer redirects to http://jira.domain.local:8080
  5. Jira login page is served, implying that the user is not logged in to Jira.
  6. User clicks a link or refreshes the page.
  7. User is logged in.
 The behavior is more disconcerting if the user starts at a custom dashboard. In that case, instead of getting the Jira login screen at step 5 they get an error message: "The dashboard you requested either does not exist or you don't have access to it. Perhaps you need to log in to see the page." Again, if the user refreshes the page they will discover that they are already logged in.

 

I'm using Jira on-prem v7.3.6 with Okta authenticator v3.0.6. I've followed the instructions in https://saml-doc.okta.com/Provisioning_Docs/Okta_Jira_Authenticator_Configuration_Guide.html, but the redirect still gives the error. 

 

Is there an extra setting I need to add to get the final destination page to refresh so it doesn't give an error? Key point: the user is logged in, they just appear not to be.
  • 2 answers
  • 1.01K views

  • silviu.muraru1.494609885910873E12 (Okta, Inc.)

    Hi,

     

    My name is Silviu and I am a Technical Support Engineer (Tier II) at Okta.

    Please just try to use the Login URL as a Default Relay State as well and I think this would be solved. Otherwise, if this is not it, might mean that the SAML requests are not hitting the endpoint of the Audience URL of the SP.

    For any further assistance please open up a case with Okta Support and get all the necessary pieces of information, if not provided yet.

     

    Wish you all the best in your work!

     

    Thank You,

    Silviu Muraru

    Technical Support Engineer | Okta Inc.
    Expand Post

  • er961 (er961)

    Thank yiu, Silviu, but I'm still having problems. How would I go about opening a case with Okta Support? The support links all point to https://support.okta.com/help (this page) and I see no way to open a ticket.
This question is closed.
Loading
Redirect post-login serves false error page