Question 700
A third-party commerce site wants to display a Salesforce-backed login widget without redirecting visitors to a full portal. Best complete IAM decision record?
Explanation
Correct Answer
“Action: Evaluate supported embedded-login options and present-day security constraints for the client and domain. Verification: Inspect origin allowlist, redirect, consent, client registration and session lifecycle. Boundary: Embedded login still requires trusted application registration, browser policy and protected token handling” addresses the access-design responsibilities in a third-party commerce site wants to display a Salesforce-backed login widget without redirecting visitors to a full portal Test against inspect origin allowlist, redirect, consent, client registration and session lifecycle; embedded login still requires trusted application registration, browser policy and protected token handling.
Incorrect Answers
“Action: Bind partner permissions and sharing to validated account/contact relationships and reconcile changes. Verification: Inspect origin allowlist, redirect, consent, client registration and session lifecycle. Boundary: A secure sign-in does not replace record-level authorization and field visibility controls” may apply to a related identity task, but it does not establish inspect origin allowlist, redirect, consent, client registration and session lifecycle for a third-party commerce site wants to display a Salesforce-backed login widget without redirecting visitors to a full portal The controlling boundary is: Embedded login still requires trusted application registration, browser policy and protected token handling.
“Action: Evaluate supported embedded-login options and present-day security constraints for the client and domain. Verification: Validate contact-account association, external user license, site membership and test record visibility. Boundary: A public site must never infer data permission merely because a page is accessible without login” may apply to a related identity task, but it does not establish inspect origin allowlist, redirect, consent, client registration and session lifecycle for a third-party commerce site wants to display a Salesforce-backed login widget without redirecting visitors to a full portal The controlling boundary is: Embedded login still requires trusted application registration, browser policy and protected token handling.
“Action: Configure supported authentication providers and a controlled registration handler for verified external identity claims. Verification: Verify site membership removal, token revocation, contact status and legitimate retention requirements. Boundary: Embedded login still requires trusted application registration, browser policy and protected token handling” may apply to a related identity task, but it does not establish inspect origin allowlist, redirect, consent, client registration and session lifecycle for a third-party commerce site wants to display a Salesforce-backed login widget without redirecting visitors to a full portal The controlling boundary is: Embedded login still requires trusted application registration, browser policy and protected token handling.