miniOrange provides a ready to use SAML solution for SonarQube. This solution ensures that you are ready to roll out secure access to your SonarQube server within minutes.
SAML Single Sign On (SSO) plugin acts as a SAML Service Provider which can be configured to establish the trust between the SonarQube and SAML capable Identity Provider to securely authenticate the user to the SonarQube application.
The plugin supports all the known IDPs like - miniOrange, ADFS, Azure AD, Google Apps, Okta, OneLogin, Salesforce, Shibboleth, SimpleSAMLphp, OpenAM, Centrify, PingOne, RSA, Oracle, Bitium and many more.
This SAML SP module is not only more flexible but also has a lot more features. We also have overcome the limitations of the existing SAML plugin.
- Signed Request
- Encrypted Assertion
Key Features
Auto Create Users
Auto-create User in SonarQube after doing SSO, if user is not present already. Allowing users to sign up automatically saves your time and efforts of creating them manually.
User Profile Mapping
Allows Just-In-Time user provisioning into SonarQube with the profile details received from IDP while performing SSO. It allows to update user profile or create the user if not present into SonarQube.
One The Fly Group Mapping
Allows you to automatically assign groups to the user after successful SSO. It requires groups receiving from IDP to be same as groups present in SonarQube.
Manual Group Mapping
Wants to manage groups in IDP, but having different names than SonarQube groups? Using Group mapping you can easily map IDP groups to the SonarQube groups.
Single Logout
When SSO users logout of SonarQube, their IDP session stays active and unattended, which might pose a security risk. The Single Logout feature helps to terminate the user's IDP session.
Force Authentication
When a user attempts SSO but already has an valid IDP session, he will not be prompted for authentication. In such cases, Force Authentication feature comes handy to enforce user to authenticate at IDP.
Free Plugin
-
On-the-fly User Creation
-
User Profile Mapping
-
Test Configuration
- SSO Binding Types
- Supported IDPs
-
Encrypted Assertion
-
On-The-Fly Group Mapping
-
Force Authentication
-
Signed Request
-
Single Logout
-
Auto Redirect to IDP
-
Customize SP Certificates
- SLO Binding Types
- Manual Group Mapping
-
NameID Formats
Features:
Premium Plugin
-
On-the-fly User Creation
-
User Profile Mapping
-
Test Configuration
- SSO Binding Types
- Supported IDPs
- Encrypted Assertion
- On-The-Fly Group Mapping
- Force Authentication
- Signed Request
- Single Logout
- Auto Redirect to IDP
- Customize SP Certificates
- SLO Binding Types
- Customize SP Certificates
- NameID Formats
Features:
Frequently Asked Questions
How is the price determined for SonarQube SAML SSO plugin?
SonarQube server licensing is based on the number of lines of code (LOC) and the same is followed for SonarQube SAML plugin. That’s why the price for SonarQube SAML SSO plugin will be based on licensed LOC count for your SonarQube server.
miniOrange license for SonarQube SAML SSO plugin will be provided as perpetual license along with 1 year maintenance cost included. You can renew the license at 50% of purchase price after the maintenance period expires.
What is included in the 1 Year Maintenance plan?
The one year maintenance plan includes:
- Latest plugin updates with new features
- Security and vulnerability fixes
- Compatibility updates
It ensures that your SonarQube SAML SSO plugin will remain up to date.
Why renew the plugin license?
As the license for SonarQube SAML SSO plugin is provided as a perpetual license, your SSO experience will be intact after the maintenance period expires. So you can keep using the SonarQube SAML plugin. But you’ll not be able to receive plugin updates. You’ll miss out plugin releases, new features, or any compatibility updates. In order to receive any update you’ll need to have a valid maintenance license.
How to configure the SonarQube SAML plugin using sonar.properties file?
As per the SonarQube convention, you’ll be able to configure any key-value in the sonar.properties file.
You can refer to the keys used in the plugin UI and configure the values for it into the sonar.properties file. Refer to the below screenshot.
Note – The priority will always be given to the configuration provided in sonar.properties file. So any changes made for the same key through UI will not take effect.