MatthewR.19140 (Customer) asked a question.
My company is going through an email change to rebrand the entire worldwide company as having the same email scheme. This email change is in response to my company having acquired the name of our company for the domain rather than @CompanynameCountry.com and some variations of that. In the process of this switch the change is causing issues with SSO logins for various apps that use emails as the username.
Our org has multiple local orgs for different countries and then an overarching org these are all connected to via org2org. Searching here and r/okta, it seems that the way some admins fixed it was by creating a custom attribute in default user type and had the old email added, then they configured login on the application to use a custom login, namely the old email. And it looks like it could work as a band-aid solution, but would this work on the overarching org level if pushed through org2org? If so how? Maybe I don't fully grasp the expression language just yet and it's possible (only recently began learning that). If not, what other options are there?
Hi @MatthewR.19140 (Customer) , thank you for contacting Okta Community.
This case, in particular, seems to have many interlinked variables. There isn't a one-click solution to this since we are talking about multiple orgs, multiple integrations, and different types of apps.
If you have a paid account, you should pursue this with the help of a Support engineer. You can open a case here.
Regards.
--
Help others in the community by liking or hitting Select as Best if this response helped you.