feat: add OIDC Native policy - #2210
Draft
spencerugbo wants to merge 3 commits into
Draft
Conversation
github-actions
Bot
added
documentation
✅ Deploy Preview will be available once build job completes!
|
vepatel
reviewed
Aug 21, 2026
| Ingress policy support is narrower than `VirtualServer` support. | ||
|
|
||
| If you need route-level control for features like JWT, OIDC, cache, or rate limiting, use `VirtualServer` and `VirtualServerRoute` instead. | ||
| If you need route-level control for features like JWT, cache, or rate limiting, use `VirtualServer` and `VirtualServerRoute` instead. |
Contributor
There was a problem hiding this comment.
lets differentiate between njs OIDC and native OIDC
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Proposed changes
Add Native OIDC Policy to VirtualServer and Ingress
Checklist
Before sharing this pull request, I completed the following checklist:
Footnotes
Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩