[JIRA] [bitbucket-branch-source-plugin] (JENKINS-34262) Support for OAuth credentials

131 views
Skip to first unread message

maxim.kulkin@gmail.com (JIRA)

unread,
Apr 14, 2016, 5:24:01 PM4/14/16
to jenkinsc...@googlegroups.com
Maxim Kulkin created an issue
 
Jenkins / Improvement JENKINS-34262
Support for OAuth credentials
Issue Type: Improvement Improvement
Assignee: Antonio Muñiz
Components: bitbucket-branch-source-plugin
Created: 2016/Apr/14 9:23 PM
Priority: Minor Minor
Reporter: Maxim Kulkin

Right now Bitbucket Source plugin requires putting personal password to be able to monitor branches. This is a security risk to expose such information. The proper way would be to create an OAuth consumer on Bitbucket side, set proper access permissions and use OAuth key+secret to authenticate to Bitbucket.

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
Atlassian logo

jake.bishop@netdudes.de (JIRA)

unread,
May 12, 2016, 10:29:02 AM5/12/16
to jenkinsc...@googlegroups.com
jake bishop commented on Improvement JENKINS-34262
 
Re: Support for OAuth credentials

Is it true that OAuth does not work at the moment? I have been trying to use them in the credentials but i keep getting:

Started
Consulting Bitbucket Team/Project
Connecting to https://bitbucket.org using xxxxxxx/****** (Credentials Name)
FATAL: Failed to recompute children of my-project
com.cloudbees.jenkins.plugins.bitbucket.api.BitbucketRequestException: HTTP request error. Status: 401: UNAUTHORIZED.

	at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getRequest(BitbucketCloudApiClient.java:416)
	at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getTeam(BitbucketCloudApiClient.java:328)
	at com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMNavigator.visitSources(BitbucketSCMNavigator.java:164)
	at jenkins.branch.OrganizationFolder.computeChildren(OrganizationFolder.java:125)
	at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:154)
	at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:122)
	at hudson.model.ResourceController.execute(ResourceController.java:98)
	at hudson.model.Executor.run(Executor.java:410)
Finished: FAILURE

jake.bishop@netdudes.de (JIRA)

unread,
May 12, 2016, 10:31:01 AM5/12/16
to jenkinsc...@googlegroups.com

Is it true that this does not work at the moment? I have been trying to use OAuth credentials an i just get:

Started
Consulting Bitbucket Team/Project
Connecting to https://bitbucket.org using xxxx/****** (xxxxx)
FATAL: Failed to recompute children of my-job
com.cloudbees.jenkins.plugins.bitbucket.api.BitbucketRequestException: HTTP request error. Status: 401: UNAUTHORIZED.

	at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getRequest(BitbucketCloudApiClient.java:416)
	at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getTeam(BitbucketCloudApiClient.java:328)
	at com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMNavigator.visitSources(BitbucketSCMNavigator.java:164)
	at jenkins.branch.OrganizationFolder.computeChildren(OrganizationFolder.java:125)
	at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:154)
	at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:122)
	at hudson.model.ResourceController.execute(ResourceController.java:98)
	at hudson.model.Executor.run(Executor.java:410)
Finished: FAILURE

amuniz@cloudbees.com (JIRA)

unread,
May 12, 2016, 10:33:01 AM5/12/16
to jenkinsc...@googlegroups.com

Yes, this issue would not be open other wise.

jake.bishop@netdudes.de (JIRA)

unread,
May 12, 2016, 10:36:03 AM5/12/16
to jenkinsc...@googlegroups.com
jake bishop updated an issue
Change By: jake bishop
Comment:
Is it true that this does not work at the moment? I have been trying to use OAuth credentials an i just get:


{code}

Started
Consulting Bitbucket Team/Project
Connecting to https://bitbucket.org using xxxx/****** (xxxxx)
FATAL: Failed to recompute children of my-job
com.cloudbees.jenkins.plugins.bitbucket.api.BitbucketRequestException: HTTP request error. Status: 401: UNAUTHORIZED.

at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getRequest(BitbucketCloudApiClient.java:416)
at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getTeam(BitbucketCloudApiClient.java:328)
at com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMNavigator.visitSources(BitbucketSCMNavigator.java:164)
at jenkins.branch.OrganizationFolder.computeChildren(OrganizationFolder.java:125)
at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:154)
at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:122)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)
Finished: FAILURE
{code}

jake.bishop@netdudes.de (JIRA)

unread,
May 12, 2016, 10:37:03 AM5/12/16
to jenkinsc...@googlegroups.com

Would it be possible to increase the prority of this issue? Our company will not allow it's use unless we can use secure authentication methods, and this plugin looks great and just what we need.

jake.bishop@netdudes.de (JIRA)

unread,
May 30, 2016, 7:14:04 AM5/30/16
to jenkinsc...@googlegroups.com

Sorry to be persistent , is there any news about this? We would very much like to be able to use this plugin. Is there any way we can help? Unfortunately we are do not have experience in jenkins development (only usage), but we are happy to contribute where possible.

me@davidham.com (JIRA)

unread,
Nov 9, 2016, 4:18:01 PM11/9/16
to jenkinsc...@googlegroups.com

At the least, could you update the landing page for this plugin to reflect the fact that it doesn't support OAuth? I worked on this for a long time before finding this ticket. As far as the Jenkins credentials page is concerned, OAuth credentials are the same as other username/password. Putting this in the README would help a lot. Thanks.

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

weynhamz@gmail.com (JIRA)

unread,
Feb 12, 2018, 1:53:03 AM2/12/18
to jenkinsc...@googlegroups.com

Same here, after enabled two factors auth, tried app passwords, won't work either.

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

chris@chrishemp.com (JIRA)

unread,
Nov 9, 2018, 4:36:02 PM11/9/18
to jenkinsc...@googlegroups.com

Having the same issue.  With SAML/SSO configured, App Passwords do not work.  

Using bitbucket-branch-source-plugin version 2.2.14

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
Reply all
Reply to author
Forward
0 new messages