Details
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
2.5.5
-
Server running Bitbucket server:
OS: Windows 2016 Std 64 bit
Running Jira core as well as Bitbucket
We have authentication for both apps handled via the Active Directory server user directory, of type "Microsoft Active Directory (Read Only, with Local Groups)".Local PC running sourcetree:
OS: Windows 10 64bit
Server running Bitbucket server: OS: Windows 2016 Std 64 bit Running Jira core as well as Bitbucket We have authentication for both apps handled via the Active Directory server user directory, of type "Microsoft Active Directory (Read Only, with Local Groups)". Local PC running sourcetree: OS: Windows 10 64bit
-
Severity 2 - Major
Description
Prior to experiencing this issue, install sourcetree using Bitbucket cloud credentials.
When Jira is set to use our AD user principle name, which is our email address (of the format firstname.lastname@pncc.govt.nz):
- Click to get a new tab.
- Select Remote
- Add an account
- Hosting service: Bitbucket server; url: http://bitbucket.pncc.govt.nz:7990; protocol: https; auth: basic; username: (style of firstname.lastname@pncc.govt.nz)
- Click refresh password
The response message in the Edit Hosting Account dialog indicates it is hitting the rest api for http://bitbucket.pncc.govt.nz:7990/rest/api/1.0/users/firstname.lastname%40pncc.govt.nz, but the url that works is the one using the slug, which is http://bitbucket.pncc.govt.nz:7990/rest/api/1.0/users/firstname.lastname_pncc.govt.nz - but if I use the slug (firstname.lastname_pncc.govt.nz) as the username in the dialog, I get an "unauthorized" error. This fault affects all users, not just myself.
When we change Jira to use a different property in AD to authenticate against, eg any one without an "@" in it such as the samaccountname, and attempt the same action, the result is as expected - we get to see the list of remote repos.
In either case, if we browse to a repo page on our Bitbucket server and click Clone, sourcetree will work as expected.
Initially logged on the product questions board, here.