# Can't add credentials to connect to BitBucket

**URL:** <https://community.jenkins.io/t/cant-add-credentials-to-connect-to-bitbucket/9709>\
**Category:** Using Jenkins\
**Tags:** question\
**Created:** [September 20, 2023, 2:59pm UTC](https://community.jenkins.io/t/cant-add-credentials-to-connect-to-bitbucket/9709 "2023-09-20T14:59:39Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![GreenZmey](https://avatars.discourse-cdn.com/v4/letter/g/e56c9b/32.png) [@GreenZmey](https://community.jenkins.io/u/GreenZmey)\
**Post date:** [September 20, 2023, 2:59pm UTC](https://community.jenkins.io/t/cant-add-credentials-to-connect-to-bitbucket/9709/1 "2023-09-20T14:59:39Z")

</div>

> **About Jankins**
>
> ## Jenkins: 2.387 OS: Windows Server 2019 - 10.0 Java: 17.0.5 - Oracle Corporation (Java HotSpot™ 64-Bit Server VM)
> 
> ace-editor:1.1  
> active-directory:2.29  
> ant:481.v7b\_09e538fcca  
> antisamy-markup-formatter:155.v795fb\_8702324  
> apache-httpcomponents-client-4-api:4.5.13-138.v4e7d9a\_7b\_a\_e61  
> atlassian-bitbucket-server-integration:3.3.2  
> bitbucket:223.vd12f2bca5430  
> bootstrap5-api:5.2.1-3  
> bouncycastle-api:2.26  
> branch-api:2.1051.v9985666b\_f6cc  
> build-timeout:1.28  
> caffeine-api:2.9.3-65.v6a\_47d0f4d1fe  
> checks-api:1.8.1  
> cloudbees-folder:6.800.v71307ca\_b\_986b  
> command-launcher:90.v669d7ccb\_7c31  
> commons-lang3-api:3.12.0-36.vd97de6465d5b\_  
> commons-text-api:1.10.0-27.vb\_fa\_3896786a\_7  
> credentials:1214.v1de940103927  
> credentials-binding:523.vd859a\_4b\_122e6  
> display-url-api:2.3.7  
> durable-task:503.v57154d18d478  
> echarts-api:5.4.0-1  
> email-ext:2.93  
> font-awesome-api:6.2.1-1  
> git:5.0.0  
> git-client:4.0.0  
> github:1.36.1  
> github-api:1.303-400.v35c2d8258028  
> github-branch-source:1696.v3a\_7603564d04  
> gradle:2.2  
> instance-identity:142.v04572ca\_5b\_265  
> ionicons-api:31.v4757b\_6987003  
> jackson2-api:2.14.1-313.v504cdd45c18b  
> jakarta-activation-api:2.0.1-2  
> jakarta-mail-api:2.0.1-2  
> javax-activation-api:1.2.0-5  
> javax-mail-api:1.6.2-8  
> jaxb:2.3.7-1  
> jdk-tool:63.v62d2fd4b\_4793  
> jjwt-api:0.11.5-77.v646c772fddb\_0  
> jquery3-api:3.6.1-2  
> jsch:0.1.55.61.va\_e9ee26616e7  
> junit:1166.va\_436e268e972  
> ldap:659.v8ca\_b\_a\_fe79fa\_d  
> locale:226.v008e1b\_58cb\_b\_0  
> mailer:438.v02c7f0a\_12fa\_4  
> matrix-auth:3.1.6  
> matrix-project:785.v06b\_7f47b\_c631  
> mercurial:1260.vdfb\_723cdcc81  
> mina-sshd-api-common:2.9.2-50.va\_0e1f42659a\_a  
> mina-sshd-api-core:2.9.2-50.va\_0e1f42659a\_a  
> momentjs:1.1.1  
> msbuild:1.30  
> nuget:1.1  
> okhttp-api:4.9.3-108.v0feda04578cf  
> pam-auth:1.10  
> pipeline-build-step:2.18  
> pipeline-github-lib:38.v445716ea\_edda\_  
> pipeline-graph-analysis:195.v5812d95a\_a\_2f9  
> pipeline-groovy-lib:629.vb\_5627b\_ee2104  
> pipeline-input-step:466.v6d0a\_5df34f81  
> pipeline-milestone-step:101.vd572fef9d926  
> pipeline-model-api:2.2118.v31fd5b\_9944b\_5  
> pipeline-model-definition:2.2118.v31fd5b\_9944b\_5  
> pipeline-model-extensions:2.2118.v31fd5b\_9944b\_5  
> pipeline-rest-api:2.28  
> pipeline-stage-step:296.v5f6908f017a\_5  
> pipeline-stage-tags-metadata:2.2118.v31fd5b\_9944b\_5  
> pipeline-stage-view:2.28  
> plain-credentials:143.v1b\_df8b\_d3b\_e48  
> plugin-util-api:2.20.0  
> popper2-api:2.11.6-2  
> resource-disposer:0.20  
> scm-api:631.v9143df5b\_e4a\_a  
> script-security:1228.vd93135a\_2fb\_25  
> snakeyaml-api:1.33-90.v80dcb\_3814d35  
> ssh-credentials:305.v8f4381501156  
> ssh-slaves:2.854.v7fd446b\_337c9  
> sshd:3.275.v9e17c10f2571  
> structs:324.va\_f5d6774f3a\_d  
> timestamper:1.21  
> token-macro:321.vd7cc1f2a\_52c8  
> trilead-api:2.84.v72119de229b\_7  
> variant:59.vf075fe829ccb  
> workflow-aggregator:590.v6a\_d052e5a\_a\_b\_5  
> workflow-api:1200.v8005c684b\_a\_c6  
> workflow-basic-steps:994.vd57e3ca\_46d24  
> workflow-cps:3601.v9b\_36a\_d99e1cc  
> workflow-durable-task-step:1217.v38306d8fa\_b\_5c  
> workflow-job:1254.v3f64639b\_11dd  
> workflow-multibranch:716.vc692a\_e52371b\_  
> workflow-scm-step:400.v6b\_89a\_1317c9a\_  
> workflow-step-api:639.v6eca\_cd8c04a\_a\_  
> workflow-support:839.v35e2736cfd5c  
> ws-cleanup:0.44

Hello, everybody!  
I have Jenkins (about it under spoiler higher) and Atlassian Bitbucket v 6.8.0 stands alone. When I creating job, I chousing “Git”, set Repository URL. And when I try set credentials, I press “Add” button. In the open window, I chouse “BitBucket personal access token” in the “Kind” field, insert token. Press “Add” again.  
And I can’t chouse this credentials in the field.  
But it credetials exist on the Settings → Manager Credantial.  
How can I add and chouse credential?

---

<div class="post-metadata">

**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\
**Post date:** [September 20, 2023, 3:14pm UTC](https://community.jenkins.io/t/cant-add-credentials-to-connect-to-bitbucket/9709/2 "2023-09-20T15:14:37Z")

</div>

> [@GreenZmey](#):
>
> I chouse “BitBucket personal access token” in the “Kind” field, insert token.

The git plugin probably does not understand Bitbucket personal access token as a credential type that it supports. The git plugin supports two credential types, username/password credentials for HTTPS access and ssh private keys for SSH access. Try using the same token to define a username / password credential.

---

<div class="post-metadata">

**Author:** ![GreenZmey](https://avatars.discourse-cdn.com/v4/letter/g/e56c9b/32.png) [@GreenZmey](https://community.jenkins.io/u/GreenZmey)\
**Post date:** [September 21, 2023, 9:04am UTC](https://community.jenkins.io/t/cant-add-credentials-to-connect-to-bitbucket/9709/3 "2023-09-21T09:04:11Z")

</div>

Hello, MarkEWaite!  
Thank’s for you ansver!

> [@MarkEWaite](#):
>
> The git plugin probably does not understand Bitbucket personal access token as a credential type

But “Kind” field - drop-down list. I selected one of srings from this list.

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/jenkins/original/2X/8/88e4d202f8957ac3c007eab5451a79b90a1377a6.png)

---

<div class="post-metadata">

**Author:** ![GreenZmey](https://avatars.discourse-cdn.com/v4/letter/g/e56c9b/32.png) [@GreenZmey](https://community.jenkins.io/u/GreenZmey)\
**Post date:** [September 21, 2023, 9:13am UTC](https://community.jenkins.io/t/cant-add-credentials-to-connect-to-bitbucket/9709/4 "2023-09-21T09:13:04Z")

</div>

And our BitBacked installed on Windows Server and we didn’t use https 😶

---

<div class="post-metadata">

**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\
**Post date:** [September 21, 2023, 10:51am UTC](https://community.jenkins.io/t/cant-add-credentials-to-connect-to-bitbucket/9709/5 "2023-09-21T10:51:54Z")

</div>

> [@GreenZmey](#):
>
> But “Kind” field - drop-down list. I selected one of srings from this list.
> 
> ![image](https://europe1.discourse-cdn.com/flex013/uploads/jenkins/original/2X/8/88e4d202f8957ac3c007eab5451a79b90a1377a6.png)

Thanks for including a screenshot. That helps me understand what you are attempting.

The screenshot you’ve provided is the page used to create a new credential. The credential creation page allows a user to create any type of credential. However, all types of credentials are not supported in all cases where a credential ID is accepted as an argument. The `withUsernamePassword` argument to the `withCredentials` step accepts a credential ID but does not support the Bitbucket personal access token credential type that is provided by the [Bitbucket server integration plugin](https://plugins.jenkins.io/atlassian-bitbucket-server-integration/).

## Pipeline syntax snippet generator

You can see it is not supported if you use the [Pipeline syntax snippet generator](https://www.jenkins.io/doc/book/pipeline/getting-started/#snippet-generator) to help you generate the syntax for the `withCredentials` Pipeline step.

The Pipeline syntax snippet generator page for `withCredentials` will look something like this on your machine (available from the “Pipeline Syntax” link on any Pipeline job) (without the highlights that I added):

 ![snippet-generator](https://europe1.discourse-cdn.com/flex013/uploads/jenkins/original/2X/4/40f2a5394d0a57e183a7f1bad36401b814adef73.png)

The git plugin documentation includes a 90 second video describing the Pipeline syntax snippet generator. The video uses the `checkout` step, but the concepts are the same for the `withCredentials` step.

[![](https://europe1.discourse-cdn.com/flex013/uploads/jenkins/original/2X/e/e8f83ad92526061b89626c40d0b79a25a1db79f9.jpeg "Pipeline Syntax for Git Plugin") ](https://www.youtube.com/watch?v=ai1kf4ihZUo)

---

<div class="post-metadata">

**Author:** ![GreenZmey](https://avatars.discourse-cdn.com/v4/letter/g/e56c9b/32.png) [@GreenZmey](https://community.jenkins.io/u/GreenZmey)\
**Post date:** [September 26, 2023, 5:30pm UTC](https://community.jenkins.io/t/cant-add-credentials-to-connect-to-bitbucket/9709/6 "2023-09-26T17:30:34Z")

</div>

Thank’s for your answer too, but our BitBucket so old. Now we are planning to update BitBucket of current version.