Collapse
Submit a Service Request
Contact Information for Technical Support
My Service Notifications
Impact of a Custom domain/vhost change on SSO
Answer ID 12734 |
Last Review Date 11/02/2023
We changed our vhost to a custom domain which is working, but why are we now having a problem logging into CP with our SSO?
Environment:
Oracle B2C Service SSO
Custom Domain vhost Change
Resolution:
If you change the domain name in the URL for your site to a custom domain, the SSO configuration within the external IdP must be updated, specifically the Assertion Consumer (ACS) URL. The ACS URL for your site will change once your custom domain is put in place and will need to be updated in the external IdP to reflect your new vhost for your site. For example, your original ACS URL for customer portal may be similar to the following:
https://mysite.custhelp.com/ci/openlogin/saml
If you put a custom domain in place, the vhost for your site changes and therefore your ACS URL for customer portal would also change. In our example below, we have put the oracle.com custom domain in place for our site so the ACS URL would change to the following example:
https://mysite.oracle.com/ci/openlogin/saml
After your custom domain is put in place, the ACS URL for your site will need to be updated within your external IdP so that it includes your new custom domain. This includes the ACS URL for customer portal as well as the ACS URL for agent login for both the .NET console and the BUI.
