User guide: Protecting an API with JSON Web Tokens (JWTs) and Kubernetes authnz using Kuadrant #119
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
guicassolato
force-pushed
the
example/oidc-k8s-auth
branch
3 times, most recently
from
f377e3c
to
d15bb73
Compare
…ubernetes authnz using Kuadrant
guicassolato
force-pushed
the
example/oidc-k8s-auth
branch
from
d15bb73
to
e199940
Compare
didierofrivia
approved these changes
Dec 21, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds proper user guide-like instructions for the sample AuthPolicy on protecting an API with authentication based on ID tokens (signed JWTs) and Kubernetes Service Account tokens, and authorization based on
Kubernetes RBAC.