Custom SSO

A custom SSO configuration allows your users to sign into Gatling Enterprise using your organization's authentication system.

Configuring a custom Single Sign-On (SSO) solution is only available on corporate plan and must be requested through our support portal.

At the moment, we only support integration with SSO systems which are accessible on the Internet, and user roles are still administered within Gatling Enterprise.

If you already have an organization on Gatling Enterprise Cloud, after configuring a custom SSO, you will need to re-invite your users and configure their roles. You will, however, keep all other existing data, such as your teams, simulations, reports, API tokens, etc.

Required information#

To handle your support request, we will need to know:

• the name and slug for your organization, visible on the organization settings page
• relevant information depending on the type of SSO system used (see below)
• a way to configure one of your users as a global admin, so that they can invite back your other users - in most cases, we will ask them to sign in once, after we have configured the SSO, to link their account

OpenID Connect (OIDC) v1.0#

If your SSO system offers OIDC v1.0 integration, it will typically publish its metadata at a well known URL, often of the form https://my-sso-server.com/.well-known/openid-configuration. To configure the SSO integration, we will need:

• the metadata URL
• the client authentications which are supported by your OIDC implementation (client secret sent as POST, Basic Auth, or JWT)
• the client ID and secret we should use to connect to the SSO

Azure Active Directory (Azure AD) using OIDC#

We recommend using OIDC to integrate with Azure AD. You will need to create an app registration for Gatling Enterprise, and configure which accounts are allowed to connect. You will then find the metadata URL in Overview > Endpoints > OpenID Connect metadata document, and you can generate a new client secret in Certificates & secrets > Client secrets.

We can then give you our redirect URI, which you will need to configure in Overview > Add a redirect URI.

Okta using OIDC#

We recommend using OIDC to integrate with Okta. You will need to create a new app integration, with sign-in method “OIDC” and application type “Web Application”. You can then copy the client ID, client secret and Okta domain (we can find the metadata URL from the domain) for the application integration you just created.

We can then give you our redirect URI, which you will need to edit in the application integration you created.

SAML v2.0#

If your SSO system offers SAML v2.0 integration, it will typically publish its Identity Provider (IdP) entity descriptor on a specific URL. To configure the SSO integration, we will need this IdP entity descriptor URL.

We can then give our Service Provider (SP) descriptor if you need to import it into your SSO system.

Google#

See Google’s guide on setting up an oAuth 2.0 app. Make sure to:

• select the user type “internal” to only allow users from your organization
• add gatling.io as an authorized domain

You will need to create a client ID of the type “web application”, with the authorized redirect URI we will provide you, then send us the client ID and client secret.

GitHub#

See GitHub’s guide on setting up an oAuth 2.0 app for an organization. Make sure to:

• configure https://cloud.gatling.io as the Homepage URL
• configure the Authorization callback URL we will provide you

You will need to generate a new client secret, then send us the client ID and client secret. We will also need your GitHub organization’s name to restrict access to users from your organization.

GitLab#

See GitLab’s guide on setting up an oAuth 2.0 app for a group. Make sure to:

• configure the redirect URI we will provide you
• enable the following scopes: api, read_user, read_api

You will need to send us the application ID and secret. We will also need your GitLab group ID to restrict access to users from your group.

Edit this page on GitHub