Pre-authorization
Nobody has claimed this yet.
- Dominant language
- Erlang
- Stars
- 303
- Forks
- 211
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 5
Description
In chef/oc-id#2 it was proclaimed:
@cnunciato: Foremost, this is excellent!
Any ideas on how we’ll handle pre-authorization (e.g. skip_authorization)?
@cnunciato followed up with:
For our own apps, I think I like skip_authorization, yeah -- maybe by some additional Boolean on Doorkeeper::Application that we'd set somehow ourselves. Apps without this property, then, would just fall back to having the additional approval step. What do you think?
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 by reviewing the linked chef/oc-id#2 discussion and the proposed skip_authorization Boolean on Doorkeeper::Application. Determine how applications would be marked for pre-authorization and what approval behavior should apply to applications without the property; done means the behavior and configuration path are defined and implemented.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, authorization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100