Question 60
A staff portal starts federation from the corporate application launcher while another flow starts at the Salesforce My Domain page. Best complete IAM decision record?
Explanation
Correct Answer
“Action: Distinguish identity-provider-initiated and service-provider-initiated SAML login entry points and their state-handling requirements. Verification: Record initial URL, authentication request, relay target and completed session destination. Boundary: Different SAML initiation patterns cannot be assumed to produce identical request validation and RelayState behavior” addresses the access-design responsibilities in a staff portal starts federation from the corporate application launcher while another flow starts at the Salesforce My Domain page Test against record initial URL, authentication request, relay target and completed session destination; different SAML initiation patterns cannot be assumed to produce identical request validation and RelayState behavior.
Incorrect Answers
“Action: Distinguish identity-provider-initiated and service-provider-initiated SAML login entry points and their state-handling requirements. Verification: Inspect federation identifier uniqueness, migration map and duplicate-user test outcomes. Boundary: A shared login does not automatically grant the same data entitlements in all applications” may apply to a related identity task, but it does not establish record initial URL, authentication request, relay target and completed session destination for a staff portal starts federation from the corporate application launcher while another flow starts at the Salesforce My Domain page The controlling boundary is: Different SAML initiation patterns cannot be assumed to produce identical request validation and RelayState behavior.
“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: Different SAML initiation patterns cannot be assumed to produce identical request validation and RelayState behavior” may apply to a related identity task, but it does not establish record initial URL, authentication request, relay target and completed session destination for a staff portal starts federation from the corporate application launcher while another flow starts at the Salesforce My Domain page The controlling boundary is: Different SAML initiation patterns cannot be assumed to produce identical request validation and RelayState behavior.
“Action: Coordinate trusted certificate rotation and test old/new key acceptance according to supported Salesforce settings. Verification: Record initial URL, authentication request, relay target and completed session destination. Boundary: Display names and mutable email addresses may be unreliable identity keys” may apply to a related identity task, but it does not establish record initial URL, authentication request, relay target and completed session destination for a staff portal starts federation from the corporate application launcher while another flow starts at the Salesforce My Domain page The controlling boundary is: Different SAML initiation patterns cannot be assumed to produce identical request validation and RelayState behavior.