Make Resource Owner Password Credentials from username/password an optional flow
Nobody has claimed this yet.
- Dominant language
- Erlang
- Stars
- 303
- Forks
- 211
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 5
Description
@jamesc once (in chef/oc-id#31) proclaimed:
Since it's inherently more risky (http://tools.ietf.org/html/rfc6749#section-4.3), we should make it configurable whether you want to allow username/password based Resource Owner Password Credentials flow.
A webapp should use the Implicit flow, and we've got support for PEM -> token in the Resource Owner Password Credentials.
Perhaps the best is to give a list of the credentials types you wish to support e.g [:password, :pem]
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
No files or tests are named in the issue. Start by reviewing the existing Resource Owner Password Credentials and PEM-to-token flows, alongside RFC 6749 §4.3, then determine how configurable credential-type support should work. Done means password-based credentials can be enabled or disabled without removing the other supported flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- erlang
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100