Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Iframe
frameborder0
height250
width700
srchttp://update.sonarsource.org/plugins/crowd.html

Your browser does not support iframes.

Compatibility matrix

Plugin

0.1

0.2

1.0

Crowd

2.0.2

2.0.2

2.0.2 - 2.2.x

Description / Features

The Sonar Crowd Plugin enables the delegation of Sonar authentication to an external system. The plugin currently supports Atlassian Crowd.

Only password-checking is done against the external system. Authorization (access control) is still fully managed in Sonar. That’s why Crowd 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

  1. Place the jar into the /extensions/plugins directory
  2. Make sure that at least one user with global administration role exists in Sonar as well as in the external system
  3. Configure sonar.properties by adding and editing the following:
    Code Block
    titleconf/sonar.properties
    #-------------------
    # Sonar Crowd Plugin
    #-------------------
    # IMPORTANT : before activation, make sure that one Sonar administrator is defined in the external system
    # Activates the plugin. Leave blank or comment out to use default sonar authentication.
    sonar.authenticator.class: org.sonar.plugins.crowd.CrowdAuthenticator
    
    # Ignore failure at startup if the connection to external system is refused.
    # Users can browse sonar but not log in as long as the connection fails.
    # When set to true, Sonar will not start if connection to external system fails.
    # Default is false.
    #sonar.authenticator.ignoreStartupFailure: true
    
    # Automatically create users (available since Sonar 2.0).
    # When set to true, user will be created after successful authentication, if doesn't exists.
    # The default group affected to new users can be defined online, in Sonar general settings. The default value is "sonar-users".
    # Default is false.
    #sonar.authenticator.createUsers: true
    
    # URL of the Crowd server (usually ends with /services/).
    crowd.url:
    
    # Crowd application name.
    # Default is 'sonar'.
    #crowd.application:
    
    # Crowd application password.
    crowd.password:
    
  4. Restart the Sonar server and check the log file for:
    No Format
    INFO  org.sonar.INFO  Authentication plugin: class org.sonar.plugins.crowd.CrowdAuthenticator
    INFO  org.sonar.INFO  Authentication plugin started
    
  5. Log in to Sonar

Troubleshooting

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

Code Block
titleconf/logback.xml
  <logger name="org.sonar.plugins.crowd">
    <level value="DEBUG"/>
    <appender-ref ref="CONSOLE"/>
    <appender-ref ref="SONAR_FILE"/>
  </logger>

Changelog

JIRA Issues
anonymoustrue
titleRelease 1.0
height90
width800
columnstype;key;summary;priority;status;resolution
urlhttp://jira.codehaus.org/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?fixfor=16911&pid=11911&sorter/field=priority&sorter/order=DESC&tempMax=1000


JIRA Issues
anonymoustrue
titleRelease 0.2
height90
width800
columnstype;key;summary;priority;status;resolution
urlhttp://jira.codehaus.org/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?fixfor=16515&pid=11911&sorter/field=priority&sorter/order=DESC&tempMax=1000


JIRA Issues
anonymoustrue
titleRelease 0.1
height120
width800
columnstype;key;summary;priority;status;resolution
urlhttp://jira.codehaus.org/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?fixfor=16079&pid=11911&sorter/field=priority&sorter/order=DESC&tempMax=1000