Question 160
A contractor federation is launched using metadata copied from a different business unit with a new assertion audience. Best complete IAM decision record?
Explanation
Correct Answer
“Action: Complete Salesforce SP and corporate IdP trust registration for entity ID, ACS destination, subject and certificate. Verification: Compare the actual assertion issuer, destination, audience, NameID format and signature chain. Boundary: A signed SAML assertion from the correct issuer can still target the wrong service provider or Salesforce user” addresses the access-design responsibilities in a contractor federation is launched using metadata copied from a different business unit with a new assertion audience Test against compare the actual assertion issuer, destination, audience, NameID format and signature chain; a signed SAML assertion from the correct issuer can still target the wrong service provider or Salesforce user.
Incorrect Answers
“Action: Complete Salesforce SP and corporate IdP trust registration for entity ID, ACS destination, subject and certificate. Verification: Review RelayState handling, target allowlists, request correlation and open-redirect tests. Boundary: Just-in-Time account creation is not a timely offboarding mechanism by itself” may apply to a related identity task, but it does not establish compare the actual assertion issuer, destination, audience, NameID format and signature chain for a contractor federation is launched using metadata copied from a different business unit with a new assertion audience The controlling boundary is: A signed SAML assertion from the correct issuer can still target the wrong service provider or Salesforce user.
“Action: Use Salesforce Login History and available SAML diagnostic evidence to classify the failure before remediation. Verification: Compare the actual assertion issuer, destination, audience, NameID format and signature chain. Boundary: Moving password verification does not automatically migrate SAML trust, MFA assurance or local authorization” may apply to a related identity task, but it does not establish compare the actual assertion issuer, destination, audience, NameID format and signature chain for a contractor federation is launched using metadata copied from a different business unit with a new assertion audience The controlling boundary is: A signed SAML assertion from the correct issuer can still target the wrong service provider or Salesforce user.
“Action: Preserve approved destination state without accepting arbitrary external redirect targets. Verification: Inspect signature validation, certificate validity, issuer ID and Salesforce SSO error logs. Boundary: A signed SAML assertion from the correct issuer can still target the wrong service provider or Salesforce user” may apply to a related identity task, but it does not establish compare the actual assertion issuer, destination, audience, NameID format and signature chain for a contractor federation is launched using metadata copied from a different business unit with a new assertion audience The controlling boundary is: A signed SAML assertion from the correct issuer can still target the wrong service provider or Salesforce user.