Question 340
A headless internal report service authenticates under a controlled integration identity with signed key material. Best complete IAM decision record?
Explanation
Correct Answer
“Action: Evaluate a supported JWT bearer or service-oriented OAuth flow with strictly managed keys, audience and least privilege. Verification: Verify signed assertion claims, token audience, issuer binding, scope and key rotation. Boundary: A JWT's signature alone does not authorize any user or resource outside the registered app and org policy” addresses the access-design responsibilities in a headless internal report service authenticates under a controlled integration identity with signed key material Test against verify signed assertion claims, token audience, issuer binding, scope and key rotation; a JWT's signature alone does not authorize any user or resource outside the registered app and org policy.
Incorrect Answers
“Action: Apply app access policies, understandable consent and administrative approval for sensitive integrations. Verification: Test code verifier/challenge, redirect registration, user grant and token exchange. Boundary: A JWT's signature alone does not authorize any user or resource outside the registered app and org policy” may apply to a related identity task, but it does not establish verify signed assertion claims, token audience, issuer binding, scope and key rotation for a headless internal report service authenticates under a controlled integration identity with signed key material The controlling boundary is: A JWT's signature alone does not authorize any user or resource outside the registered app and org policy.
“Action: Plan new OAuth integrations with the external client app framework and confirm exception procedures only when genuinely needed. Verification: Verify signed assertion claims, token audience, issuer binding, scope and key rotation. Boundary: A public client cannot rely on an embedded long-term secret as a confidential client would” may apply to a related identity task, but it does not establish verify signed assertion claims, token audience, issuer binding, scope and key rotation for a headless internal report service authenticates under a controlled integration identity with signed key material The controlling boundary is: A JWT's signature alone does not authorize any user or resource outside the registered app and org policy.
“Action: Evaluate a supported JWT bearer or service-oriented OAuth flow with strictly managed keys, audience and least privilege. Verification: Compare supported release, SAML settings, service provider registration and permission assignments. 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 verify signed assertion claims, token audience, issuer binding, scope and key rotation for a headless internal report service authenticates under a controlled integration identity with signed key material The controlling boundary is: A JWT's signature alone does not authorize any user or resource outside the registered app and org policy.