Question 120
A firm changes its Experience Cloud authentication hostname and expects external identity providers to keep redirecting correctly. Best complete IAM decision record?
Explanation
Correct Answer
“Action: Plan domain and redirect URI migration across identity providers and supported Salesforce endpoints. Verification: Inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover. Boundary: A branding or domain change can break authentication even when user credentials and permissions have not changed” addresses the access-design responsibilities in a firm changes its Experience Cloud authentication hostname and expects external identity providers to keep redirecting correctly Test against inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover; a branding or domain change can break authentication even when user credentials and permissions have not changed.
Incorrect Answers
“Action: Distinguish identity-provider-initiated and service-provider-initiated SAML login entry points and their state-handling requirements. Verification: Review relying-party requirements, scopes, claims, token audiences and redirect flow. Boundary: A branding or domain change can break authentication even when user credentials and permissions have not changed” may apply to a related identity task, but it does not establish inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover for a firm changes its Experience Cloud authentication hostname and expects external identity providers to keep redirecting correctly The controlling boundary is: A branding or domain change can break authentication even when user credentials and permissions have not changed.
“Action: Plan domain and redirect URI migration across identity providers and supported Salesforce endpoints. Verification: Verify provisioning feed events, assignment mapping, timing and reconciliation of failures. Boundary: Even a correctly authenticated external subject must not gain access to another tenant's records by default” may apply to a related identity task, but it does not establish inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover for a firm changes its Experience Cloud authentication hostname and expects external identity providers to keep redirecting correctly The controlling boundary is: A branding or domain change can break authentication even when user credentials and permissions have not changed.
“Action: Separate authentication, authorization and accountability responsibilities before selecting the federation pattern. Verification: Inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover. Boundary: A successful identity-provider change does not guarantee relying applications automatically trust the replacement key” may apply to a related identity task, but it does not establish inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover for a firm changes its Experience Cloud authentication hostname and expects external identity providers to keep redirecting correctly The controlling boundary is: A branding or domain change can break authentication even when user credentials and permissions have not changed.