SonarQube 7.8 Integration with Windows Active Directory

SonarQube Server / Community Build
, ,
1

Hi ,

I have set up the following with docker-compose, and the server is running well.

  1. SonarQube 7.8
  2. Postgresql 10

The case is , I am trying to integrate SonarQube with my own active directory through LDAP. Previously, i understand that we got to download a plugin before it can be integrated successfully, but i read that the plugin only support up to SonarQube 7.3.

I am referring the latest documentation , https://docs.sonarqube.org/display/PLUG , and there are no listing for ldap plugin.

I assume that the support for LDAP(Active Directory) with SonarQube have ceased?

Robin

2

Hi @robincher and welcome to this community !

LDAP is still supported, you can see the documentation about it here : https://next.sonarqube.com/sonarqube/documentation/instance-administration/delegated-auth/#ldap-authentication
By the way, the documentation is now embedded into SonarQube, you can have access by going to : https://<YOUR_SONARQUBE_URL>/documentation/instance-administration/delegated-auth/#ldap-authentication

Regards

3

Hi Julien,

Thanks for the quick reply!

As the current environment doesn’t allow me to proxy out to the internet yet, i gotta do a manual install of the ldap plugins first.

Let me test out and if it works then we can close this. Possibly, also share what i did to the community here.

Additionally, just a side questions, is there any good practices in managing configurations for containers?

Should i copy the configuration and build my own container image, or i can do a persistent volume mount?

Dockerfile

FROM sonarqube:7.8-community

COPY sonar.properties /opt/sonarqube/conf/
COPY /plugins/ /opt/sonarqube/plugins/

docker run -v /opt/sonarqube/conf:/opt/sonarqube/conf:z sonarqube:latest
4

You don’t need to install the LDAP plugin, it’s already bundled when downloading SonarQube.

About your remaining questions about containers, please open a new thread in order to respect our guidelines.

Thanks

5

Hi,

Sure thanks. I solved it by setting the corrrect permission on the volume mount for the /extension folder. Previously it was set as root, and i realised the container required it to be run as user sonarqube.

I encountered another issue with regards to setting java trusted store within the container,but as suggested i will raised a new topic.

Robin

6

Thanks for sharing how you’ve solved this first issue !

7

How did you resolved this ?Could you provide some steps

I solved it by setting the corrrect permission on the volume mount for the /extension folder. Previously it was set as root, and i realised the container required it to be run as user sonarqube