Message-ID: <2082589993.1117.1432772490634.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_1116_859526245.1432772490634" ------=_Part_1116_859526245.1432772490634 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Out of the box, SonarQube comes with a complete mechanism to man= age security (authentication + authorization). Configuring security allows = you to cover two main use cases:
Here are examples of security restrictions you can enforce by configurin= g security in SonarQube:
Authentication and authorization can also be delegated to an external sy= stem: LDAP or Active Directory with the SonarQube LDAP Plugin, PAM with the SonarQube PAM Plugin or Crowd&nb= sp;with the SonarQube Crowd Plugin<= /a>. SSO is also supported through the SonarQube OpenID plugin.
Another aspect of security is the encryption of settings such as passwor= ds. SonarQube provide a built-in mechanism to encrypt settings.