Bitbucket enterprise way - LDAP

Posted on Mon 20 January 2020 in Bitbucket

Bitbucket is tool of choice in many large companies. One reason for that is it has nice integration with other part of ecosystem like Jira - most often.

By definition it’s ‘just another git server’. It has server side git and UI. Basic choice here to be taken is: SaaS (hosted within or Self-Hosted. With self-hosted comes following: “Single server or “data center” version?”

“Data Center” is suited for international organisations which would get profit from Mirrors.

Bitbucket screen

Domain integration

Natural element of introducing Bitbucket in bigger company is the tit will be connected with Domain. From domain it will be authenticating user access (in general and for specific project).

How to setup LDAP read?

Main page to answer that question would be: Connecting Bitbucket Server to an existing LDAP directory

Here beside creating read connection with LDAP would be to setup filter which will prevent user and group flood. By that I mean:

  • Bitbucket has user access license - therefore it’s good to control who need access? Jane from HR can be most often confused but idea of such app.

  • Groups like distribution lists most often are not needed to be indexed by Bitbucket.

Too open configuration will have impact on application w/o real reason for that. In short: it will be Mistake.


General configuration

Advanced settings

From general useful options are:

  • Nested Groups
  • Filter out expired users
  • Enable incremental synchronisation

User settings

User settings

Important part here is: User Object Filter


Above filter out all users which are member of given group - in that case Bitbucket_Users_Login.

Group settings

Group settings

Group Object Filter:


Above will fetch all groups with attribute: ‘extensionAttribute1’ set to Bitbucket. Simple way to sync only those groups which were nominated to be used within Bitbucket.