This article contains information on how to configure the logging in process with SAML in case of the Auth0.

General requirements and limitations

Logging into GitProtect using SAML-integrated identity providers should be initiated from the GitProtect panel.

Do not log in from the IdP panel (e.g. from the Auth0 panel) to the application defined for GitProtect.

Do not test the integration from the IdP panel (e.g., from the Azure panel), as this will initiate a login from the IdP panel.


In the Auth0 Admin dashboard: Go to Dashboard > Applications > Applications and hit Create SSO Integration

In the Create application window specify the application name and select application type: Regular Web Applications

Next hit the Create button Scroll to the bottom of the Settings page and click Advanced Settings

Select the Endpoints tab and locate SAML Metadata URL. Copy and save it. You will need to provide it to the Gitprotect.

Scroll to the top and select the Addons tab and enable SAML2 Web App toggle.

On the Settings tab, enter the Application Callback URL. See below

https://GitProtectManagementServiceURL/Auth/AssertionConsumerService where: GitProtectManagementServiceURL - URL address to your GitProtect Management Service.

On the Settings window scroll to the down and uncomment the lines 31,32,33.

At the “callback” parameter (line 32), type the Logout URL.

Logout URL: https://GitProtectManagementServiceURL/auth/SAMLLogoutResponse where: GitProtectManagementServiceURL - URL address to your GitProtect Management Service

Scroll to the bottom of the tab and click Enable.

GitProtect side

Log into the GitProtect Web panel, go to the Settings tab and open the External Identity Providers section. Click Add new provider button and fill in the details.

At first, Name, which is your own custom name - i.e. Auth0, then Entity ID, so in this example, it is XoperoAuth0 (Application name that we’ve set on the Auth0 side).

Next, paste the link of IdP metadata into the Metadata URL field.

Set up a default Language and Role for the users with proper permissions and it's done! You can now log out of your account and test the configuration with your configured integration.

More about the Roles in GitProtect you can see in the following article:

pageRoles and permissions

Last updated