Require a redirect flow for end_session endpoint handling
Open
Nobody has claimed this yet.
enhancement
question
- Dominant language
- TypeScript
- Stars
- 1k
- Forks
- 165
- PR merge metrics
- No merged PRs in 30d
Description
I've forked here and added support for the end_session endpoint similar to the existing authorize endpoint. It's working for my purposes.
Rather than submit a pull request, and in the spirit of the contributing guidelines, I thought I'd best ask if this is the direction you want to go?
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.
Research direction
Start with the fork's dev branch and compare the proposed end_session support with the existing authorize endpoint. Review the requested redirect flow and determine the maintainers' intended direction before changing the SDK. Done means end_session handling follows the accepted design and works for the relevant OpenID Connect provider flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100