Two custom domains with SSO

0
I know it's possible for an environment to have TWO custom domains. BUT is it possible to do this if you need SSO for both domains?   If I have http://myapp1.com as one custom domain, in order to set up SSO (with Azure as our IDP), I use the SAML module with the below settings. The entity ID appears to be pulled from the ApplicationRootUrl value in the custom runtime settings.   If I set up a new custom domain, myapp2.com I can add that domain just fine. The problem is, in this particular screen below, I can only have a single entity ID.  Will the new custom domain still work with the same SSO settings? Will it redirect my users from myapp2.com to myapp1?   
asked
1 answers
0

So I got SSO setup from our network team for myapp2.com (not the real host name, obviously). I can confirm that when going to myapp2.com/SSO it just redirects to myapp1.com

 

I have logic in the app the reads the application URL and has logic that depends upon this URL. Is there any way to keep the second domain?

 

Also, I created a second IDP configuration in the SAML module for this new domain. Once I activated it (now having two active IDP configurations), The original url (myapp1.com) took users to a page with an error message that read "cannot validate SAML message".

answered