Question 320
A reporting portal wants a signed OIDC ID token from a Salesforce identity provider rather than SOAP assertion processing. Best complete IAM decision record?
Explanation
Correct Answer
“Action: Evaluate Salesforce as an OIDC provider for a compatible relying party with approved claims and client registration. Verification: Verify issuer discovery, token validation, audience, nonce and redirect URI handling. Boundary: An OAuth API access token is not a substitute for validating an OIDC identity token at the relying party” addresses the access-design responsibilities in a reporting portal wants a signed OIDC ID token from a Salesforce identity provider rather than SOAP assertion processing Test against verify issuer discovery, token validation, audience, nonce and redirect URI handling; an OAuth API access token is not a substitute for validating an OIDC identity token at the relying party.
Incorrect Answers
“Action: Fix authorization-code redirect registration, state integrity and callback matching before widening trusted origins. Verification: Test allowed resources, user permission sets, sensitive fields and scope restrictions. Boundary: An OAuth API access token is not a substitute for validating an OIDC identity token at the relying party” may apply to a related identity task, but it does not establish verify issuer discovery, token validation, audience, nonce and redirect URI handling for a reporting portal wants a signed OIDC ID token from a Salesforce identity provider rather than SOAP assertion processing The controlling boundary is: An OAuth API access token is not a substitute for validating an OIDC identity token at the relying party.
“Action: Evaluate Salesforce as an OIDC provider for a compatible relying party with approved claims and client registration. Verification: Test code verifier/challenge, redirect registration, user grant and token exchange. Boundary: IdP-initiated and SP-initiated SAML have different request context and cannot be assumed equivalent” may apply to a related identity task, but it does not establish verify issuer discovery, token validation, audience, nonce and redirect URI handling for a reporting portal wants a signed OIDC ID token from a Salesforce identity provider rather than SOAP assertion processing The controlling boundary is: An OAuth API access token is not a substitute for validating an OIDC identity token at the relying party.
“Action: Separate identity claims validation from API token handling and enforce correct issuer, audience and nonce checks. Verification: Verify issuer discovery, token validation, audience, nonce and redirect URI handling. Boundary: A valid Salesforce user session does not authorize a SAML assertion for an unrelated target audience” may apply to a related identity task, but it does not establish verify issuer discovery, token validation, audience, nonce and redirect URI handling for a reporting portal wants a signed OIDC ID token from a Salesforce identity provider rather than SOAP assertion processing The controlling boundary is: An OAuth API access token is not a substitute for validating an OIDC identity token at the relying party.