{iframe:src=http://update.sonarsource.org/plugins/ldap.html|width=700|height=250|frameborder=0}
Your browser does not support iframes.
{iframe}

Compatibility Matrix

- means that it has been successfully tested

Description

The Sonar LDAP Plugin enables the delegation of Sonar authentication and authorization to an external system. The plugin currently supports LDAP and Microsoft Active Directory.

The main features of the plugin are:

• Password checking against the external authentication engine
• Automatic synchronization of usernames and emails
• Automatic synchronization of the relationships between users and groups (authorization)
• Ability to authenticate the user both against the external or internal authentication systems (technical Sonar user accounts have no need for instance to be defined in the LDAP server)

By default there is no need to firstly create a user account in the Sonar DB to allow a user to log into Sonar. During the first authentication trial, if the password is correct, the Sonar DB is automatically populated with the new Sonar user. Moreover, each time a user logs into Sonar, the username, the email and the groups this user belongs to are automatically refreshed in the Sonar DB.

About the delegation of authorization, there is only one pre-requisite: the relationships between users and groups are only synchronized with groups which are already defined in Sonar. So groups and related permissions must be first defined in Sonar.

Usage & Installation

1. Install the LDAP plugin through the Update Center or download it into the SONAR_HOME/extensions/plugins directory
2. Restart the Sonar server
3. Make sure that at least one user with global administration role exists in Sonar as well as in the external system

4. Configure the LDAP plugin by editing the conf/sonar.properties file (see below)

5. Restart the Sonar server and check the log file for:

   INFO org.sonar.INFO Security realm: LDAP
   ...

   INFO o.s.p.l.LdapContextFactory Test LDAP connection: OK

6. Log into Sonar

(&(objectClass=inetOrgPerson)(uid={login}))

(&(objectClass=user)(sAMAccountName={login}))

(&(objectClass=groupOfUniqueNames)(uniqueMember={dn}))

(&(objectClass=group)(member={dn}))

# LDAP configuration
sonar.security.realm=LDAP
sonar.security.savePassword=true

ldap.url=ldap://myserver.mycompany.com
 
ldap.user.baseDn=ou=Users,dc=mycompany,dc=com
ldap.user.objectClass=inetOrgPerson
ldap.user.loginAttribute=uid
ldap.user.realNameAttribute=cn
ldap.user.emailAttribute=mail


ldap.group.baseDn=ou=Groups,dc=sonarsource,dc=com
ldap.group.request=(&(objectClass=posixGroup)(memberUid={uid}))

Here is description of how auto-discovery works:

1. Determine DNS Domain Name:
   • from "ldap.realm" property if set
   • from FQDN of machine, where Sonar is installed (eg. if FQDN is "sonar.example.org", then DNS Domain Name will be "example.org")
2. Determine 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":

     _ldap._tcp.example.org. 72784 IN SRV 0 5 389 ldap.example.org.

     for this domain URL of LDAP server will be "ldap://ldap.example.org:389"

3. 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")

Authentication Methods

• Simple
  Simple authentication is not recommended for production deployments not using the secure ldaps protocol as it sends a cleartext password over the network.
• Anonymous
  Used when only needs read-only access to non-protected entries and attributes when binding to the LDAP server.
• CRAM-MD5
  The Challenge-Response Authentication Method (CRAM) based on the HMAC-MD5 MAC algorithm (RFC 2195).
• DIGEST-MD5
  This is an improvement on the CRAM-MD5 authentication method (RFC 2831).
• GSSAPI
  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.

For a full discussion of LDAP authentication approaches, see RFC 2829 and RFC 2251.

Known Limitations

Auto-discovery takes into account only one SRV record.

Troubleshooting

You can enable debug logging by adding the following to conf/logback.xml:

<logger name="org.sonar.plugins.ldap">
  <level value="DEBUG"/>
  <appender-ref ref="CONSOLE"/>
  <appender-ref ref="SONAR_FILE"/>
</logger>

Migration from plugin version 1.0 to version 1.1.1

Perform the following replacements:

Configure Group Mapping: at least by specifing new mandatory property - "ldap.group.baseDn".

Change Log