MaikuB / MaikuB/flutter_appauth
Add support for Pushed Authorization Requests (RFC9126)
Nobody has claimed this yet.
- Dominant language
- Objective-C
- Stars
- 308
- Forks
- 301
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 5
Description
I'm working on an app, using `flutter_appauth` to perform the Authorization Code flow.
Our authorization server supports [Pushed Authorization Requests (PAR)](https://datatracker.ietf.org/doc/html/rfc9126), which is favorable for us over standard Authorization Requests, because it ensures confidentiality, integrity, and authenticity of the request data, as it doesn't use a browser to perform the (initial) request.
Are there any plans to add this as a feature to the project?
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 flutter_appauth's Authorization Code flow and compare the wrapper surface with the AppAuth iOS and Android SDKs, using RFC9126 as the behavioral reference. Determine whether PAR can be exposed on both platforms and define the required API and tests; the issue is done when the support scope and acceptance criteria are clear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, dart, flutter, ios
- Domain
- authentication, mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100