OIDC NJS / Native module comparison doc
@y82 is already working on this.
Since Sep 29, 2025.
- Dominant language
- HTML
- Stars
- 94
- Forks
- 174
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 66
Description
With the gradual release train of the new dynamic module for OIDC, there is a lot of mis-understanding that:
- The Dynamic OIDC module is feature complete
- the NJS module is deprecated
Neither of these statements are true.
However, customers are implementing the new dynamic module and finding it lacking in capabilities that are present in the NJS implementation.
Also, the two will never truly have parity, but the dynamic module will provide a better implementation (all that the NJS implementation never was).
Describe the solution you'd like
A doc that indicates that there are two implementations, what they support today.
This will need to be maintained as the dynamic module advances in capabilities.
AFAIK, the capabilities of the NJS implementation is not well documented. How to implement is.
Describe alternatives you've considered
We currently do nothing.
At any point in time this doc will appear to favor one OIDC implementation over another, this is fine if it helps customers solve their problems today. And find the better implementation for their needs today.
Additional context
Add any other context or screenshots about the feature request here.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.