support for OIDC implicit flow
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 431
- Forks
- 179
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 71
Description
Solution
Add configurable support for the OIDC Implicit Flow. The draft PR #1879 has a work-in-progress changeset.
Describe alternatives you've considered
Not supporting the implicit flow
Use of the OIDC Implicit Flow is discouraged by the standards body and IAM providers. That said, some use cases may require it. The proposed change does not change the current behavior for the default OIDC Authorization Code Flow.
Additional context
The implementer's guide is the principal reference. Okta also provides an illustrative guide.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reviewing draft PR #1879 and the OpenID Connect Implicit Flow implementer's guide referenced in the issue. Confirm how configurable support should fit alongside the existing Authorization Code Flow, and identify the relevant tests or entry points in that changeset. Done means the implicit flow is supported when configured while default behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100