Extend PKCE flow to support RFC8707
Nobody has claimed this yet.
- Dominant language
- Objective-C
- Stars
- 2k
- Forks
- 867
- Avg merge
- 4d 48m
- Merged PRs (30d)
- 1
Description
Is your feature request related to a problem you're having? Please describe.
Want to implement Login via PKCE flow, but need resource parameter as added in RFC 8707. As far as I can see AppAuth-iOS does not support the resource parameter right now.
Describe the solution you'd like
Implement RFC8707 to AppAuth-iOS
Describe alternatives you've considered
Use other iOS AuthN library capable of handling resource parameter in PKCE flow
Additional context
As introduction of RFC8707 states, RFC6479 was extended to limit possible audiences among other advantages.
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
The issue names the PKCE flow and RFC 8707 but no source files, tests, or entry points. Start by locating the AppAuth-iOS PKCE request construction and review RFC 8707's resource parameter requirements. Done means the SDK supports the resource parameter in PKCE requests with corresponding coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, objective-c
- Domain
- authentication, mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100