Skip to content
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

Fixed OAuth connection to enterprise API #389

Merged
merged 2 commits into from
Oct 28, 2017

Conversation

iraleigh
Copy link

I see that the change to OAuth was made a long time ago. I just started using this library at work, and we use GitHub Enterprise.

When connecting with OAuth, I was getting a failure on the connection when using GitHub.connectToEnterprise(apiUrl, oauthAccessToken) I noticed that there was no option to use login. I thought this was strange and tried to get to the bottom of it.

The reason I have proposed the fix in this way was so that I didn't break the existing functionality (I don't think it was functioning as intended, but if it has gone this long without fixing I have to assume it is working for someone). That is why I didn't touch the existing method.

I am new to this project, so if there is more that I need to do for this to meet your requirements, please let me know.

@@ -178,6 +178,10 @@ public static GitHub connectToEnterprise(String apiUrl, String oauthAccessToken)
return new GitHubBuilder().withEndpoint(apiUrl).withOAuthToken(oauthAccessToken).build();
}

public static GitHub connectToEnterpriseWtihOAuth(String apiUrl, String login, String oauthAccessToken) throws IOException {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

with

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oops

@KostyaSha
Copy link
Contributor

Why you can't call Builder directly and build with arguments that you need?

@iraleigh
Copy link
Author

iraleigh commented Oct 24, 2017

That is what have done as a work around, but I figured I would raise this change and see if anyone else has had this problem.

@KostyaSha if this is not a common problem, then I will close this PR and continue using my own workaround.

@kohsuke kohsuke merged commit 46dce17 into hub4j:master Oct 28, 2017
kohsuke added a commit that referenced this pull request Oct 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants