Question 40
A public-sector agency will accept signed assertions from a separately administered identity domain. Best complete IAM decision record?
Explanation
Correct Answer
“Action: Define trusted issuer, certificate or signing-key verification, audience and endpoint registration before enabling federation. Verification: Inspect signed metadata, certificate rotation plan, assertion audience and ACS URL. Boundary: A signed message from an unknown issuer or the wrong audience must not automatically authenticate a Salesforce user” addresses the access-design responsibilities in a public-sector agency will accept signed assertions from a separately administered identity domain Test against inspect signed metadata, certificate rotation plan, assertion audience and ACS URL; a signed message from an unknown issuer or the wrong audience must not automatically authenticate a Salesforce user.
Incorrect Answers
“Action: Define trusted issuer, certificate or signing-key verification, audience and endpoint registration before enabling federation. Verification: Follow the login redirects, assertion issuer and target audience. 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 inspect signed metadata, certificate rotation plan, assertion audience and ACS URL for a public-sector agency will accept signed assertions from a separately administered identity domain The controlling boundary is: A signed message from an unknown issuer or the wrong audience must not automatically authenticate a Salesforce user.
“Action: Distinguish identity assertions from API authorization grants and use a suitable authenticated identity protocol when user login is required. Verification: Inspect signed metadata, certificate rotation plan, assertion audience and ACS URL. Boundary: OIDC authentication and OAuth resource authorization solve related but different requirements” may apply to a related identity task, but it does not establish inspect signed metadata, certificate rotation plan, assertion audience and ACS URL for a public-sector agency will accept signed assertions from a separately administered identity domain The controlling boundary is: A signed message from an unknown issuer or the wrong audience must not automatically authenticate a Salesforce user.
“Action: Evaluate Just-in-Time user creation versus pre-provisioning based on lifecycle and entitlement needs. Verification: Inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover. Boundary: A signed message from an unknown issuer or the wrong audience must not automatically authenticate a Salesforce user” may apply to a related identity task, but it does not establish inspect signed metadata, certificate rotation plan, assertion audience and ACS URL for a public-sector agency will accept signed assertions from a separately administered identity domain The controlling boundary is: A signed message from an unknown issuer or the wrong audience must not automatically authenticate a Salesforce user.