I’ve been reading through the documentation here for configuring IdP routing rules for the purpose of federating with the IdP of one of my company’s clients. They are asking for the ability to connect to a custom subdomain (https://ourcustomername.ourname.com) and have that automatically direct them to their IdP for authentication purposes rather than having to wait to provide their email address as in the “User matches” routing condition described in the documentation. Is it possible to perform routing based on the domain name the user initially accessed?
What’s this subdomain associated with? Is that were certain SSO applications are hosted? Would matching based on application accessed work for your use case?
1 Like
I think that was the bit of information I was missing. I’m newer to identity management and Okta and wasn’t seeing the application based routing as something I could use to control it. Am I correct in thinking that I can set up an application for this external client, create a subdomain for it, set up that subdomain to use my website that is using Okta and use that custom subdomain in the redirect URIs of my application and that will allow for routing by application?
1 Like