Moving from Okta SSO to Ping ID

[Mark Youssef]

Hello,

Is there clear instructions on how to move the SSO From OKta to Ping ID? Also the possible risks associated to it?

IE: 

1) Do users have to log off and log back on?

2) What will be the possible impact to end users? 

3) How will the interaction with end-users look like?

Thank You!

[Jim Knepley - ReleaseTEAM · Accepted solution]

Hi @Mark Youssef, welcome to the community.

Users probably won't need to log off and back in immediately, but they will eventually in the normal course of operation.

I could see complications in mapping user groups as part of the SAML assertion as Ping is notoriously difficult to configure. Since you've got a premium license, you should be able to test your Ping configuration in your sandbox first.

The end-user interaction is very similar, if not identical, just a different identity provider.

[Mark Youssef]

Thanks Jim. Do you happen to foresee any other possible issues that might arise before we start the process? 

[Jim Knepley - ReleaseTEAM]

Just one other thing...

Assuming that you're using SCIM for user provisioning... when you disable the integration with Okta, I'm not sure what that will do.

If you disable it on the Okta side first, it might signal Atlassian to disable or remove the accounts. If you disable the Atlassian side first, your accounts will probably stay, but what happens when you enable SCIM on the Ping side is anybody's guess.