Question 20
A B2C shopping site needs customer identity claims at sign-in while its separate fulfillment API needs delegated access. Best complete IAM decision record?
Explanation
Correct Answer
“Action: Select OIDC for identity assertions and OAuth authorization flows for scoped API access when supported by the participants. Verification: Review relying-party requirements, scopes, claims, token audiences and redirect flow. Boundary: OIDC authentication and OAuth resource authorization solve related but different requirements” addresses the access-design responsibilities in a B2C shopping site needs customer identity claims at sign-in while its separate fulfillment API needs delegated access Test against review relying-party requirements, scopes, claims, token audiences and redirect flow; OIDC authentication and OAuth resource authorization solve related but different requirements.
Incorrect Answers
“Action: Distinguish identity-provider-initiated and service-provider-initiated SAML login entry points and their state-handling requirements. Verification: Review relying-party requirements, scopes, claims, token audiences and redirect flow. Boundary: Cryptographic signature validity alone cannot make an assertion with the wrong audience acceptable” may apply to a related identity task, but it does not establish review relying-party requirements, scopes, claims, token audiences and redirect flow for a B2C shopping site needs customer identity claims at sign-in while its separate fulfillment API needs delegated access The controlling boundary is: OIDC authentication and OAuth resource authorization solve related but different requirements.
“Action: Select OIDC for identity assertions and OAuth authorization flows for scoped API access when supported by the participants. Verification: Follow the login redirects, assertion issuer and target audience. Boundary: A successful identity-provider change does not guarantee relying applications automatically trust the replacement key” may apply to a related identity task, but it does not establish review relying-party requirements, scopes, claims, token audiences and redirect flow for a B2C shopping site needs customer identity claims at sign-in while its separate fulfillment API needs delegated access The controlling boundary is: OIDC authentication and OAuth resource authorization solve related but different requirements.
“Action: Evaluate delegated authentication versus federated SSO in the context of current support, trust and credential-handling requirements. Verification: Test first login, required attributes, inactive status, license assignment and onboarding delay. Boundary: OIDC authentication and OAuth resource authorization solve related but different requirements” may apply to a related identity task, but it does not establish review relying-party requirements, scopes, claims, token audiences and redirect flow for a B2C shopping site needs customer identity claims at sign-in while its separate fulfillment API needs delegated access The controlling boundary is: OIDC authentication and OAuth resource authorization solve related but different requirements.