Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 40 Next »

Description / Features

This plugin enables the delegation of SonarQubeauthentication to underlying PAM subsystem. The plugin works on *nix box with Pluggable Authentication Module (PAM).

Only password-checking is done against PAM. Authorization (access control) is still fully managed in SonarQube. A SonarQube account must be created first for each new user wishing to use SonarQube. The System administrator should also assign the user to the desired groups in order to grant him necessary rights. If exists, the password in the SonarQubeaccount will be ignored as the external system password will override it.

Works on

OS and Architecture

Works

Linux AMD64

(tick)

Linux i386

(tick)

Mac OS X PPC

(warning)

Solaris sparc

(warning)

Windows all flavours

(minus)

(tick) Works, tested
(warning) Should work, not tested
(minus)  Does not work

Usage & Installation

  1. Install jpam
    1. Download jpam for your system from here
    2. Alternatively:
      1. Copy the jpam's native library following these directions
      2. Copy the jpam's native libray in sonar/bin/<your arch>/lib
  2. Install SonarQube PAM plugin
    1. Place the jar plugin into the /extensions/plugins directory
    2. Make sure that at least one user with global administration role exists in SonarQubeas well as in the external system
    3. Update the SONARQUBE_HOME/conf/sonar.properties file by adding the following lines:

      sonar.properties
  3. Restart SonarQube and check logs for:

  4. Log in to SonarQube

Known Issues

Crash using PAM winbind authentication (pam_winbind.so)

In case of unsucessful login for wrong password/locked out account (wrong username does not produce the same issue) you may get this kind of error while using pam winbind authentication:

pam_winbind.so error

In this case SonarQube crashes and restarts automatically.

As far as I understand it's a pam_winbind.so issue. I've found this workaround:

  1. Edit /etc/security/pam_winbind.conf:
  2. Set Kerberos authentication:

    /etc/security/pam_winbind.conf

Change Log

Loading

Release 0.2 (1 issues)

 

Loading

Release 0.1 (1 issues)

 

 

  • No labels