- means that it was tested
The Sonar LDAP Plugin enables the delegation of Sonar authentication to an external system. The plugin currently supports LDAP and Microsoft Active Directory.
Only password-checking is done against the external system. Authorization (access control) is still fully managed in Sonar. That’s why LDAP or Active Directory users do not automatically have access to Sonar. A Sonar account must be created first for each new user wishing to use Sonar. The Sonar administrator should also assign the user to the desired groups in order to grant him necessary rights. If exists, the password in the Sonar account will be ignored as the external system password will override it.
Usage & Installation
- Download the plugin from Update Center and restart server. If you don't have access to Internet, then manually download JAR file into $SONAR_HOME/extensions/plugins and restart server.
- Make sure that at least one user with global administration role exists in Sonar as well as in the external system
Configure conf/sonar.properties by adding and editing the following:
Restart the Sonar server and check the log file for:
- Log in to Sonar
Here is description of how auto-discovery works:
- Determining DNS Domain Name:
- from "ldap.realm" property if set
- from FQDN of machine, where Sonar installed (eg. if FQDN is "sonar.example.org", then DNS Domain Name will be "example.org")
- Determining URL of LDAP server:
- from "ldap.url" property if set
from DNS server ( see known limitations ), here is example of SRV Record for domain "example.org":
for this domain URL of LDAP server will be "ldap://ldap.example.org:389"
- Determining BaseDN:
- from "ldap.baseDn" property if set
- from DNS Domain Name (eg. if DNS Domain Name is "example.org", then BaseDN will be "dc=example,dc=org")
Simple authentication is not recommended for production deployments not using the secure ldaps protocol as it sends a cleartext password over the network.
Used when only needs read-only access to non-protected entries and attributes when binding to the LDAP server.
The Challenge-Response Authentication Method (CRAM) based on the HMAC-MD5 MAC algorithm (RFC 2195).
This is an improvement on the CRAM-MD5 authentication method (RFC 2831).
GSS-API is Generic Security Service API (RFC 2744). One of the most popular security services available for GSS-API is the Kerberos v5, used in Microsoft's Windows 2000 platform.
Auto-discovery takes into account only one SRV record.
You can enable debug logging by adding the following to conf/logback.xml:
com.atlassian.confluence.macro.MacroExecutionException: JIRA project does not exist or you do not have permission to view it.
Release 1.0 (1 issues)
Release 0.1 (8 issues)
|SONARPLUGINS-302||Support Microsoft Active Directory||Closed||Fixed|
|SONARPLUGINS-301||Authenticate users against an LDAP server||Closed||Fixed|
|SONARPLUGINS-300||Support SASL GSSAPI authentication||Closed||Fixed|
|SONARPLUGINS-299||Support SASL Digest-MD5 authentication||Closed||Fixed|
|SONARPLUGINS-297||Publish source code||Closed||Fixed|
|SONARPLUGINS-304||Support SASL CRAM-MD5 authentication||Closed||Fixed|