search

bower / registry

The Bower registry
https://registry.bower.io/packages
MIT License
292 stars 66 forks source link

Github login #49

Closed wibblymat closed 9 years ago

wibblymat commented 10 years ago

As mentioned at a meeting recently, it would be good to delegate user management to someone else. Github is a logical choice for us.

The API uses OAuth2, and offers a method for checking that a user is a collaborator on a repo - handy for letting people take ownership of current packages when we add auth.

There is a snag though. There are two ways that a user could log in from the command line. The first is that they can give the bower client their github username and password directly. The second involves redirecting the user to the github webpage to finishing authorisation. Neither feels great. Do we have any alternatives, or preferences for which of these we use?

@satazor @benschwarz @svnlto @paulirish @sindresorhus @necolas

svnlto commented 10 years ago

handy for letting people take ownership of current packages when we add auth.

+1

I know https://modulus.io/ use the cli way of logging you into github, feels ok ( not too obtrusive ) so I'd vote on that.

sindresorhus commented 10 years ago

:+1:

Could use https://github.com/rvagg/ghauth

wibblymat commented 10 years ago

@sindresorhus Awesome! I was trying to find something like that and failing. Looks perfect.

wibblymat commented 10 years ago

WIP viewable at https://github.com/wibblymat/registry/compare/refactor...github-auth?expand=1

sindresorhus commented 10 years ago

@wibblymat can you submit the PR? easier to give feedback that way.

desandro commented 9 years ago

Closing now that Bower v1.4.0 has shipped with bower login