Question 400
A partner service provider relies on outdated Salesforce IdP metadata after an approved certificate change. Best complete IAM decision record?
Explanation
Correct Answer
“Action: Coordinate Salesforce IdP signing certificate rollover with service providers and preserve fallback verification. Verification: Check signing key fingerprint, metadata published to partners, trust-update status and login smoke tests. Boundary: Rotating a signing certificate without coordinating trust at the SP can interrupt every affected sign-in” addresses the access-design responsibilities in a partner service provider relies on outdated Salesforce IdP metadata after an approved certificate change Test against check signing key fingerprint, metadata published to partners, trust-update status and login smoke tests; rotating a signing certificate without coordinating trust at the SP can interrupt every affected sign-in.
Incorrect Answers
“Action: Coordinate Salesforce IdP signing certificate rollover with service providers and preserve fallback verification. Verification: Validate token type, signature trust, issuer, subject, audience and replay context. Boundary: Client credentials does not implicitly represent an individual interactive user or bypass org authorization” may apply to a related identity task, but it does not establish check signing key fingerprint, metadata published to partners, trust-update status and login smoke tests for a partner service provider relies on outdated Salesforce IdP metadata after an approved certificate change The controlling boundary is: Rotating a signing certificate without coordinating trust at the SP can interrupt every affected sign-in.
“Action: Apply app access policies, understandable consent and administrative approval for sensitive integrations. Verification: Check signing key fingerprint, metadata published to partners, trust-update status and login smoke tests. Boundary: Salesforce can issue trusted SAML assertions only for applications and subjects registered in its identity provider trust configuration” may apply to a related identity task, but it does not establish check signing key fingerprint, metadata published to partners, trust-update status and login smoke tests for a partner service provider relies on outdated Salesforce IdP metadata after an approved certificate change The controlling boundary is: Rotating a signing certificate without coordinating trust at the SP can interrupt every affected sign-in.
“Action: Evaluate Salesforce as an OIDC provider for a compatible relying party with approved claims and client registration. Verification: Test allowed resources, user permission sets, sensitive fields and scope restrictions. Boundary: Rotating a signing certificate without coordinating trust at the SP can interrupt every affected sign-in” may apply to a related identity task, but it does not establish check signing key fingerprint, metadata published to partners, trust-update status and login smoke tests for a partner service provider relies on outdated Salesforce IdP metadata after an approved certificate change The controlling boundary is: Rotating a signing certificate without coordinating trust at the SP can interrupt every affected sign-in.