Details
-
Bug
-
Resolution: Tracked Elsewhere
-
Medium
-
None
-
2
-
Major
-
Description
Issue Summary
While the Atlassian Cloud app within Okta does now provide a Statuspage chiclet, you are not provided with an example URL from Atlassian on what to submit while setting up the app in Okta.
Atlassian provides examples for services like Jira (https://[your-subdomain].atlassian.net) and Confluence (https://[your-subdomain].atlassian.net/wiki) but nothing is provided to customers looking to configure it for Statuspage. Maybe the issue is that the management URL is not on an Atlassian domain?
Steps to Reproduce
- setup Atlassian cloud Okta app
- provide a URL for the Statuspage chiclet to point to manage.statuspage.io in order to be taken to the management console
- get dumped at https://manage.statuspage.io/login
- type in email address again (defeating purpose of SSO id-init flow)
- get into management portal
Expected Results
The Statuspage chiclet in okta authenticate, and direct, you to the Statuspage management portal (manage.statuspage.io)
Actual Results
The IdP flow directs you to https://manage.statuspage.io/login where you are forced to enter your email address, instead of being sent into the management portal.
Workaround
Customers can provide the below URL (replacing the cloud site info section from the example) when setting up the chiclet. This will allow for expected behavior when doing an IdP init session -
manage.statuspage.io/cloud/atlassian-cloud-site-id
While this does solve the issue, it is not convenient to find a given Atlassian site URL, and is not provided in the existing Atlassian Cloud Okta app setup documentation: https://saml-doc.okta.com/SAML_Docs/How-to-Configure-SAML-2.0-for-Atlassian-Cloud.html
Attachments
Issue Links
- relates to
-
ACCESS-830 Update Atlassian Cloud App in Okta to include Trello, Bitbucket, Statuspage and OpsGenie Chiclets
- Closed