BobL.86708 (Customer) asked a question.
Let's say you have an Okta org, and you have an SSO integration with G Suite.
Now let's say you rename your Okta org. Are you then unable to log into your G Suite account until you update your SSO settings? If so, how do you go about updating the settings on the G Suite side, given that you're now locked out?
For G Suite specifically, you need to download a cert from Okta and upload it in the Google Admin console. I suppose it's possible that the cert will continue to work after you rename your org. But what if that's not the case, and I need to generate and upload a new cert?
Is this general scenario possible, where you can no longer log into an application after changing your Okta org name, and the only way to fix it is to log into the application and update settings (which of course you can't do)? If it is possible, what do you do to avoid it?
Hello @BobL.86708 (Customer),
Please check the following link with information:
https://support.okta.com/help/s/article/Renaming-your-Okta-Subdomain?language=en_US
If you see on the document:
Regards,
Natalia
Okta Inc.
Thank you for the link, I did read the article but am still a bit unsure on how to proceed. Do I need to update each application with the corrected Okta subdomain before the Okta subdomain itself is changed?
My concern is that if I wait until after the Okta subdomain has changed, how would I then log into the application to update the SSO settings?