You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
For illustration purposes, we have a user1 that is granted access to Jira and another user2 that is not granted access to Jira but is granted access to Confluence. The organization that these two users are employed with are using Okta as an IAM solution that will enable SAML SSO for Jira application users (user1) ONLY.
Due to the requirement above, user1 will be assigned the Atlassian application to follow the SAML SSO login workflow but user2 will not be assigned any Atlassian applications. As such, user2 will not be able to login to Confluence by:
1) Logging into Okta as no Atlassian applications are assigned to user2; or
2) Directly logging in through the Atlassian Login page as this will trigger SP-initiated SSO which brings user2 to Okta where no Atlassian application is assigned to the user.
Are there any configurations that we can perform on Atlassian that can allow user2 to access Confluence without having to be redirected to Okta, perhaps through a customization of separate login pages? If not, any alternative options are appreciated.