-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement hex web auth flow #21
Comments
Just to note, I've neglected this, but purposefully. There should be a new mentors group and our plans for GSOC for these things might do well in there. That said, I wouldn't want to wait a long time before doing this. |
I have added an issue to Hex.pm: hexpm/hexpm#1024 that hopefully gives some more context. It doesn't have a detailed specification, such would hopefully be created as part of working on a proof-of-concept. |
The Hexpm team is looking for a means of authenticating a hex client from the browser. The plan is to default to this new means of authentication and deprecate the Username/Password authentication. The github cli (https://github.com/cli/cli) had a similar problem. What they did was implement the device OAuth flow (https://datatracker.ietf.org/doc/html/rfc8628). I decided that a flow of that sort would work very well for Hexpm. However, Hexpm has no support for OAuth. So, I can only "mock" the device flow. This commit does the following: - Adds all the endpoints at the router for such a flow - Creates a controller - Add support for step 1 of the device flow - Adds tests for the above functionality See also: hexpm#1024, erlef/build-and-packaging-wg#21
The Hexpm team is looking for a means of authenticating a hex client from the browser. The plan is to default to this new means of authentication and deprecate the Username/Password authentication. The github cli (https://github.com/cli/cli) had a similar problem. What they did was implement the device OAuth flow (https://datatracker.ietf.org/doc/html/rfc8628). I decided that a flow of that sort would work very well for Hexpm. However, Hexpm has no support for OAuth. So, I can only "mock" the device flow. This commit does the following: - Adds all the endpoints at the router for such a flow - Creates a controller - Add support for step 1 of the device flow - Adds tests for the above functionality See also: hexpm#1024, erlef/build-and-packaging-wg#21
Background
Per #18 we have agreed to move forward with implementing a web auth token flow implemented in hex.pm and utilized by mix hex and rebar3_hex.
Tasks
The following tasks must be completed to resolve this issue.
Related agenda items, issues, and pull requests.
The text was updated successfully, but these errors were encountered: