0kp09 (0kp09) asked a question.
Hello,
I have integrated JIRA and Okta. When I log into Okta first, I am automatically logged into JIRA without having to enter my credentials again. However, if I log into JIRA first, I am redirected to log into Okta again. I would like to eliminate the need for this second login.
Thank you,
Marcela
Hi! Great question. What I beleive you are referring to is the user experience difference between IdP initiated vs. Service Provider (SP) initiated.
In the example above, the Service Provider would be JIRA and the IdP is Okta. If navigating from Okta to JIRA is a single login beginning with Okta, this is the typical IdP initiated user experience. The login session is transferred to JIRA as a pre-existing trust relationship has been configured between the two.
Service Provider login will re-direct users back to Okta for authentication once they supply their username, as the domain will help JIRA identify the appropriate Okta org to re-direct the request to. Once re-directed, the user will need to login, where (if successful) they will be re-directed back to JIRA.
This second user experience is what is expected on how users would authenticate to JIRA, using Okta, when navigating to JIRA first. If they are in a browser session in which they are already authenticated, then I would probably expect this re-direct would not be needed. But if opening up an incognito window or something similar, you would need to authenticate again.
Please let me know if you have any further questions or concerns - thanks!
Hello there! Thank you for your response. I have another question related to this topic. If I am already logged into Okta and I click on a JIRA ticket link in an email, it opens in a new tab in the same browser. However, I am prompted to log into JIRA even though I am already logged into Okta. Is it necessary/mandatory to open JIRA within the Okta dashboard first or is there a configuration that can be adjusted to prevent this?
Thank you.
From what I understand, and I could be wrong, but this is going to be dictated by the length of your session. For instance, if you just log in and then click the link, does it do the same? I have this behavior occasionally when using ServiceNow or some equivalent and as long as I am still logged on in an active session, re-authentication is not needed. Otherwise, this may be a setting in JIRA that I am unaware of. This is typically all dictated by the session cookie that is in your browser.
Finally, Be sure to check your sign-on policy as well for any setting that might shorten your session lifetime too much
Configure an Okta Sign-On Policy
@0kp09 (0kp09) As @DonF.81354 (Customer) told, when the JIRA session is timeout or not have activate JIRA session，it will rediret to Okta. you can set JIRA as both Okta and APP in Okta App setting. use can click JIRA icon in Okta to login JIRA.
We use cookies to provide the best website experience and to help understand marketing efforts. We may also share data with ad partners to reach potential customers across the web. To learn more, visit our Privacy Policy. Click here for Your Privacy Choices. You may also opt out of this sharing by signaling your preference via GPC, applicable only to the browser signaling the opt-out.
More information
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
Select All
We use cookies to provide the best website experience and to help understand marketing efforts. We may also share data with ad partners to reach potential customers across the web. To learn more, visit our Privacy Policy. Click here for Your Privacy Choices. You may also opt out of this sharing by signaling your preference via GPC, applicable only to the browser signaling the opt-out.
More information
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
Select All
Hi! Great question. What I beleive you are referring to is the user experience difference between IdP initiated vs. Service Provider (SP) initiated.
In the example above, the Service Provider would be JIRA and the IdP is Okta. If navigating from Okta to JIRA is a single login beginning with Okta, this is the typical IdP initiated user experience. The login session is transferred to JIRA as a pre-existing trust relationship has been configured between the two.
Service Provider login will re-direct users back to Okta for authentication once they supply their username, as the domain will help JIRA identify the appropriate Okta org to re-direct the request to. Once re-directed, the user will need to login, where (if successful) they will be re-directed back to JIRA.
This second user experience is what is expected on how users would authenticate to JIRA, using Okta, when navigating to JIRA first. If they are in a browser session in which they are already authenticated, then I would probably expect this re-direct would not be needed. But if opening up an incognito window or something similar, you would need to authenticate again.
Please let me know if you have any further questions or concerns - thanks!