Question 210
A supplier sends a SAML assertion with a display name but no stable subject attribute for Salesforce account mapping. Most decisive verification?
Explanation
Correct Answer
“Inspect signed subject, unique mapping field, duplicate-name tests and account resolution logs” distinguishes sign-in from entitlement administration in a supplier sends a SAML assertion with a display name but no stable subject attribute for Salesforce account mapping It checks whether agree on an unambiguous NameID or federation identifier claim before accepting the identity.
Incorrect Answers
“Inspect FederationIdentifier values, SAML NameID, duplicate users and first-login creation trace” needs to be evaluated against A supplier sends a SAML assertion with a display name but no stable subject attribute for Salesforce account mapping. The relevant check is Inspect signed subject, unique mapping field, duplicate-name tests and account resolution logs; Display name, address or shared email alias is not a safe primary unique identity key.
“Correlate HR termination event, Salesforce active status, refresh tokens and existing sessions” needs to be evaluated against A supplier sends a SAML assertion with a display name but no stable subject attribute for Salesforce account mapping. The relevant check is Inspect signed subject, unique mapping field, duplicate-name tests and account resolution logs; Display name, address or shared email alias is not a safe primary unique identity key.
“Validate OIDC issuer, client settings, callback, verified user claims and registration handler outcomes” needs to be evaluated against A supplier sends a SAML assertion with a display name but no stable subject attribute for Salesforce account mapping. The relevant check is Inspect signed subject, unique mapping field, duplicate-name tests and account resolution logs; Display name, address or shared email alias is not a safe primary unique identity key.