-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Support web-based OAuth flow for Enterprise authentication #384
Comments
I don't know what a CAS backend is. GitHub has two different types of authentication:
hub uses GitHub API, so it needs to exchange your username/password for OAuth keys. This has nothing to do with git protocol over SSH, and SSH keys can't help here. I suspect that whatever CAS is, it means you don't have a regular GH Enterprise username/password that you can pass on the command-line. Not sure how to work around this |
Correct, we authenticating against an external authentication scheme. So we On Mon, Aug 26, 2013 at 9:23 AM, Mislav Marohnić
|
Here's a person who had the same issue and solved it manually #293 (comment) I understand that this is hackish and confusing. I'll look into how to support the web-based OAuth flow in case there's no username/password. However, in the meantime you're on your own |
Thanks On Mon, Aug 26, 2013 at 9:29 AM, Mislav Marohnić
|
While a more permanent solution is being developed, link to the workaround so that people can continue to use hub in their GHE environments. Related-Bug: mislav#826 Related-Bug: mislav#384
Even if user/pass hypothetically did work for some user I haven't yet encountered, they could get an access token just as easily as anyone else, so I wonder why the command-line tool couldn't just prompt for the access token instead of user/pass, and let the people who haven't made one yet make one specifically for the tool. |
Any update on this open issue? |
Hi,
I am trying to use with GitHub Enterprise, however it keeps asking for a username and password. We are using the CAS backend.
Thanks!
The text was updated successfully, but these errors were encountered: