OpenID Connect (OIDC) handles authentication: it helps verify who a user is. In a token-based identity architecture, an identity provider manages identities and issues verifiable tokens, so applications need not store users’ passwords. section 11.3.2
Passport or valet key?
Think of OIDC as a digital passport that helps prove who you are. OAuth 2.0 is more like a valet key: it concerns what you’re allowed to access. They work together, but answer different questions. section 11.3.2
Figure 11.3 The IdP issues the "Royal Seal" (JWT), which the API Gateway verifies to ensure the user is who they claim to be.
The identity provider issues a JWT, and the API gateway verifies it to check the user’s claimed identity. section 11.3.2













