Skip to main content
SonarQube is a code quality and security analysis platform. Connect your SonarQube instance to Oleria to bring user and group access into your identity and access graph, without a dedicated SonarQube-specific integration.

​
What Oleria discovers

  • User accounts and profile attributes synced from SonarQube’s directory.
  • Groups and their memberships.
Oleria uses this data for dormant account detection and access reviews, refreshed on SonarQube’s standard sync schedule.

​
Prerequisites

  • Admin access in SonarQube with permission to create a service account and generate a user token.
  • Admin access on the Oleria platform to add a new integration.
The exact location of these settings can change over time. If the steps below don’t match what you see, refer to SonarQube’s own API documentation.

​
Get your SCIM credentials from SonarQube

1

Create a service account in SonarQube

Sign in to SonarQube as an admin, go to Administration → Security → Users, and create a service account with browse permissions.
2

Copy your SCIM Base URL and Authentication token

Generate a user token for the service account, then copy both values before you leave the page - you’ll paste them into Oleria in the next section:
  • SCIM Base URL - the HTTPS API endpoint for your SonarQube instance.
  • Authentication token - the user token you generated.
Copy the token now. Many applications display it only once. Store it securely and rotate it per your organization’s security policy.

​
Connect SonarQube to Oleria

1

Open the integration

Go to your Oleria workspace, select Integrations, then select the SonarQube tile.
2

Complete the connection form

Select Continue and fill in the connection form:
3

Save the integration

Select Connect to validate the credentials and save the integration.

​
Verify the integration

Confirm the new instance appears in your Oleria workspace under Connected Integrations with a status of Healthy. Oleria syncs users and groups from SonarQube on the standard SCIM provisioning schedule once the initial sync completes.
If SonarQube rotates your user token, update the Authentication token in Oleria by editing the integration.

​
Governance actions

Oleria can also invoke lifecycle actions in SonarQube when the token you provide has write access:
  • Enable or disable a user account
  • Add or remove a user from a group
  • Create a new user or group
Many teams start with a read-only token for visibility, then grant write access once they’re ready to automate remediation in SonarQube.

​
Contact us

For questions about this integration, contact us at support@oleria.com.