[JIRA] (JENKINS-51276) Erroneous credential issue with upgrade from 2.2.8 to 2.2.9 version of Bitbucket Branch Source Plugin

[dholmes@netapp.com (JIRA)]

NetAppBlueDevil created an issue

Jenkins / JENKINS-51276 Erroneous credential issue with upgrade from 2.2.8 to 2.2.9 version of Bitbucket Branch Source Plugin Issue Type: Bug Assignee: Unassigned Components: bitbucket-branch-source-plugin Created: 2018-05-11 19:41 Environment: Jenkins 2.120 Bitbucket Server 5.8.2 Priority: Blocker Reporter: NetAppBlueDevil When upgrading from 2.2.8 to 2.2.9 of this plugin, my configured pipeline no longer functioned. When I went in to look at the configuration, within the Bitbucket server portion, this message was displayed under the Repository Name field - "The selected credentials do not have permission to determine whether devts-bb does or does not exist." My credential is a username/password for a user with write access on the repository and up through the 2.2.8 version of this plugin has worked just fine for obtaining the code and updating the build status.  Because of this issue, the pipeline no longer executes when Bitbucket changes happen in the repo. Add Comment

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

[dholmes@netapp.com (JIRA)]

NetAppBlueDevil commented on JENKINS-51276

Re: Erroneous credential issue with upgrade from 2.2.8 to 2.2.9 version of Bitbucket Branch Source Plugin I think I have determined the issue with this.  For some reason I was having to initially configure my Bitbucket endpoint using URL that included my user name.  That worked fine through the 2.2.8 release, but broke at 2.2.9.  In configuring a new Jenkins system and using the 2.2.11, I think I discovered that this is in fact the issue  and removing the user@ from the URL solves the issue with the newer plugin version for me. It also appears that the user that I use in Jenkins requires admin level permissions as well to my repository.  That was not required either at the 2.2.8 plugin level. Commenting on this to help anyone else who encountered the same issue. I think that this plugin still does require clearer documentation of the expected permissions needed to function.  This seems like a high permission level to require for a Jenkins CI level system.

Add Comment

[dholmes@netapp.com (JIRA)]

NetAppBlueDevil updated an issue

Jenkins / JENKINS-51276

Erroneous credential issue with upgrade from 2.2.8 to 2.2.9 version of Bitbucket Branch Source Plugin

Change By: NetAppBlueDevil Priority: Blocker Minor

Add Comment

[sweety21387@gmail.com (JIRA)]

Nidhi Patel commented on JENKINS-51276

Re: Erroneous credential issue with upgrade from 2.2.8 to 2.2.9 version of Bitbucket Branch Source Plugin I tried downgrading the plugin to 2.2.8 but I am still hitting the same issue. "The selected credentials do not have permission to determine whether <project_key> does or does not exist." I do not have any user name in URL of bitbucket. Can someone help me?

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[maikel.bloemendal@delem.com (JIRA)]

Maikel Bloemendal commented on JENKINS-51276

Re: Erroneous credential issue with upgrade from 2.2.8 to 2.2.9 version of Bitbucket Branch Source Plugin

I experienced the same error after upgrading our bitbucket server instance, I needed to login to Bitbucket with the credentials, but got an additional captcha challenge. After logging in everything worked as expected.

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[acxmatos@yahoo.com.br (JIRA)]

Antonio Matos commented on JENKINS-51276

Re: Erroneous credential issue with upgrade from 2.2.8 to 2.2.9 version of Bitbucket Branch Source Plugin

Not sure if it's related to this particular plugin, but I also had issues setting up a multi branch pipeline connected to our on premises Bitbucket Server. In my case, we use a corporate internet proxy to manage Jenkins plugins. For some reason, this proxy was being used by the Bitbucket plugin during the credential validation call, resulting in an invalid authentication (401). I could find the following on Jenkins fine logs, which led me to solve the problem: Jan 23, 2020 5:09:06 PM FINE com.cloudbees.jenkins.plugins.bitbucket.server.client.BitbucketServerAPIClient Using proxy authentication (user=xxx) Jan 23, 2020 5:17:11 PM FINE com.cloudbees.jenkins.plugins.bitbucket.api.credentials.BitbucketUsernamePasswordAuthenticator Add host=http://x.x.x.x:7990 to authCache. As you can see, the BitbucketServerAPIClient class was using the proxy to make an internal call. In the Manage Plugin advanced settings, I just added the Bitbucket Server IP address to the "No Proxy Host" list, and the issue went away.

Add Comment