Curated articles, resources, tips and trends from the DevOps World.
Summary: This is a summary of an article originally published by The New Stack. Read the full original article here →
https://www.linkedin.com/in/iggbom/ When building security solutions using OAuth and OpenID Connect (OIDC), we frequently discuss tokens. Using tokens means applications don’t have to maintain a static API key or, even worse, hold a username and password.
In contrast to the access token and the refresh token, an ID token is always a JSON Web Token (JWT).
The Phantom Token pattern combines a JWT and an opaque token issued to the (public) application.
This fills the purpose of the opaque token in the Phantom Token approach, and the client uses this as its access token.
Made with pure grit © 2024 Jetpack Labs Inc. All rights reserved. www.jetpacklabs.com