Hello,
We found that if we keep any user in an SSO enforce authentication policy then they can access our organization's Confluence with Okta, as Okta and our organization's confluence are integrated, but they can not access other organizations' confluence without our Okta. When they are trying to access other organizations' confluence they are redirected to our Okta login page, and thus they are unable to access other confluence without Okta. They need to login into their Okta account to access other organizations' confluence as well.
So the scenario is, suppose we have a user "kamrun.nahar@mitutoyo.co.jp", and this user is assigned to our organization's Confluence application through Okta, and she is in the SSO enforcement authentication policy in our organization's confluence. So, she will access "onemitutoyodevops.atlassian.net" through Okta. This doesn't create any problem with accessing our organization confluence.
But being a member of SSO enforce authentication policy in our confluence, while this user is trying to access another organization's confluence like "newnisha.atlassian.net", they are redirecting to the Okta login page and they need to login to an Okta account to access another organization's confluence as well.
We know this can be solved by keeping this user out of the SSO enforcement policy, but in this case, the user needs to access our organization's confluence without Okta.
But we don't want manual login (don't want without Okta login) for this user in our confluence "onemitutoyodevops.atlassian.net". But we want the user to access the other organizations' confluence without facing the above problems.
Please help us with this asap. Thanks in advance.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.