jaredhanson / jaredhanson/oauth2orize
oauth2orize.exchange.password with HTTP Basic scheme
- Dominant language
- JavaScript
- Stars
- 3.5k
- Forks
- 472
- PR merge metrics
- No merged PRs in 30d
Description
oauth2orize.exchange.password requires username and password request params in url, but if i want to protect the `token` endpoint with basic http authentication (which is more secure than ClientPasswordStrategy), there is no way to exchange encrypted username:password key pair in headers for access token. Any suggestions?
Contributor guide
Research direction
Start at oauth2orize.exchange.password and the token endpoint, then compare the current URL username/password parameters with the requested HTTP Basic header flow. No files or tests are named; done would require a decided way to exchange Basic-authenticated credentials for an access token.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, authentication
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100