OpenID Connect (SaaS)

Instructions in this section are specific to cloud-based (SaaS) Sysdig environments. If you are configuring an on-premises Sysdig environment, refer to OpenID Connect (On-Prem) instead.

OpenID support in the Sysdig platform allows authentication via your choice of Identity Provider (IdP). This section describes how to integrate and enable OpenID Connect with both Sysdig Monitor and Sysdig Secure.


Using OpenID with Sysdig

The Sysdig platform ordinarily maintains its own user database to hold a username and password hash. OpenID instead allows for redirection to your organization’s IdP to validate user credentials and other policies necessary to grant access to Sysdig applications. Upon successful authentication via OpenID, a corresponding user record in the Sysdig platform’s user database is automatically created, though the password that was sent to the IdP is never seen nor stored by the Sysdig platform.

Enable OpenID

1. Know which IdP your company uses and will be configuring.

These are the OpenID Providers for which Sysdig has performed detailed interoperability testing and confirmed how to integrate using their standard docs. If your OpenID Provider is not listed (including ones that do not support OpenID Connect Discovery), it may still work with the Sysdig platform. Contact Sysdig Support for help.

  1. Okta (OpenID)
  2. Google Cloud Authentication (OpenID)
  3. OneLogin (OpenID)
  4. Keycloak (OpenID)
  5. Azure (OpenID)

2. Decide the login flow you want users to experience.

Contact Sysdig for the Company Name associated with your account.

  1. Sysdig SaaS URL - On the main Sysdig login page select the OpenID button and enter your company name.

  2. Direct URL - Access the URL directly from a browser:

    1. Monitor: <Monitor Region URL>/api/oauth/openid/COMPANY_NAME
    2. Secure: <Secure Region URL>/api/oauth/openid/COMPANY_NAME?product=SDS

Replace the <Monitor Region URL> and <Secure Region URL> with a valid URL from SaaS Regions and IP Ranges.

  1. IdP-Initiated Login - Log in from an IdP interface.

    The individual IdP integration pages describe how to add Sysdig to the IdP interface. You will need your Company Name on hand.

3. Configure your IdP and collect the resulting config attributes.

Collect the metadata URL (or XML) and test it. If you intend to configure IdP-initiated login flow, you need the configure the Redirect URI. See Redirect URI.

4. Configure Sysdig

  1. Log in to Sysdig Monitor or Sysdig Secure and configure authentication.
    • Log in to Sysdig Monitor Settings (as super admin) and enter the necessary configuration information in the UI. Save and Enable OpenID as your SSO.
    • Log in to Sysdig Monitor Settings (as super admin) and enter the necessary configuration information in the UI. Save and Enable OpenID as your SSO.
  2. Repeat the process for the other Sysdig product, if you are using both Monitor and Secure. Enter a separate redirect URI in your IdP for each product; otherwise, the integration processes are the same.

Configure IdP in Sysdig

Choose Your IdP

Select the appropriate IdP link below, and follow the instructions:

  1. Okta (OpenID)
  2. Google Cloud Authentication (OpenID)
  3. OneLogin (OpenID)
  4. Keycloak (OpenID)
  5. Azure (OpenID)

Enter OpenID Connection Settings

  1. Log in to Sysdig Monitor or Sysdig Secure as administrator and select Settings from the user menu.

  2. Select Authentication(SSO) > OpenID.

  3. Enter the relevant parameters and click Save Settings.

Connection SettingDescription
Client IDThe unique ID provided by your IdP.
Client SecretThe secret provided by your IdP.
Issuer URLThe URL provided by your IdP. For example:</. Use the entire domain path for OpenID Connect, including any trailing /.
Create user on loginEnable to allow creating users on login. Otherwise only existing users can login. Default: Enabled.
Metadata DiscoveryIdP supports Metadata Discovery. Default: Enabled.
Disable username and password loginPrevent users from logging in using username and password (require IdP login).
Toggle Enable OpenID single logoutFlag to enable single logout. See Configure OpenID Single Logout.
Use External IDRequire customer specific External ID in Redirect URI. See Use External ID in Redirect URI
Group MappingUse Group Mapping. See Group Mappings
Group Attribute NameFor use with Group Mapping. See Group Mappings
Additional Scopes*The additional scopes required for logging in. The mandatory scopes are openid, profile, and email. You do not need to enter these as additional scopes, only any additional scopes beyond these three.

Okta, OneLogin, and Keycloak support metadata auto-discovery; so these settings should be sufficient for these IdPs.

(Optional) Enter OpenID Additional Settings

In some cases, an OpenID IdP may not support metadata auto-discovery, and additional configuration settings must be entered manually.

In this case:

  1. In the OpenID tab, toggle the Metadata Discovery button to off to display additional entries on the page.

  2. Enter the relevant parameters derived from your IdP and click Save.

Connection Setting


Issuer URL

Required parameter. This value is often the same Issuer URL, but can be different for providers that have a separate general domain and user-specific domain

For example, general domain:, user-specific domain:

The URL provided by your IdP. For example, Ensure that you use the entire domain path for OpenID Connect, including any trailing /.

Authorization Endpoint

Required. Authorization request endpoint.

Token Endpoint

Required. Token exchange endpoint.

JSON Web Key Set Endpoint

Required. The endpoint that contains key credentials for token signature verification.

End session endpoint

Optional. The URL at the IdP to which a Relying Party (RP) can perform a redirect to request that the end user be logged out at the IdP.

This option is required if the single-logout toggle is enabled.

Token Auth Method

Authentication method.

Supported values:


client_secret_post (case insensitive)

Select OpenID for SSO

  1. Select OpenID from the Enabled Single Sign-On dropdown.

  2. Click Set Authentication.

  3. Repeat the entire enablement process for Sysdig Monitor or Sysdig Secure, if you want to enable both applications.

Redirect URI

Identify the correct Redirect URI associated with your Sysdig application and region.

RegionAppSign-In Redirect URIs

For more information on regions, see SaaS Regions and IP Ranges.

Use External ID in Redirect URI

In order to improve security, the option to enable customer specific (unique, generated), External ID was introduced. The ID is automatically generated for each customer and can’t be modified. External ID is in UUID format - xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.

When the option to use External ID is enabled, the External ID must appended to the Redirect URI. The format is as follows: <REDIRECT_URI>/<EXTERNAL_ID>. Replace <REDIRECT_URI> with actual Redirect URI and <EXTERNAL_ID> with actual External ID.

See Main Authentication Settings to retrieve your External ID.

The use of External ID is going to be required after July 1st 2024. After this date it won’t be possible to disable the toggle and the toggle will be removed from the UI. It is recommended to switch your IdP to Redirect URI with External ID in your settings as soon as possible.

Configure OpenID Single Logout

With Single Logout (SLO), users only need to sign out of one service provider, and all the active sessions will be terminated without any additional effort. This is vastly convenient from a usability perspective.

SLO Process

Sysdig requests that the IdP logs the end user out by redirecting the user’s User Agent to the IdP’s Logout Endpoint. The IdP’s endpoint can be retrieved via the end_session_endpoint element of the IdP’s Discovery response (metadata). After a logout has been performed, the User Agent associated with the user will be redirected to the Sysdig login page.

Configure IdP

Configure Sign-out redirect URIs:

Configure Sysdig

  1. Log in to Sysdig Monitor or Sysdig Secure as an administrator.

    For on-prem deployments, log in as the super admin.

  2. Navigate to Settings > Authentication(SSO), and select OpenID under Connection Settings.

  3. Enter the OpenID configuration.

  4. Ensure that Enable OpenID single logout is toggled on.

  5. Click Save Settings.

  6. Select OpenID from the Enable Single Sign On drop-down, and click Set Authentication.

Login Experience

As noted in the enablement workflow above, you can offer users three ways to log in with an OpenID configuration:

Sysdig SaaS URL

Users can begin at the Sysdig SaaS URL and click the OpenID button.

See SaaS Regions and IP Ranges and identify the correct SaaS URL associated with your Sysdig application and region. For example, the URLs of Monitor and Secure for US East are:



For other regions, the format is https://<region> Replace <region> with the region where your Sysdig application is hosted. For example, for Sysdig Monitor in the EU, you use

They will be prompted to enter a Company Name, so the Sysdig platform can redirect the browser to your IdP for authentication.

Direct URL

You can provide an alternative URL to avoid the user having to enter a company name, in the format:

IdP-Initiated Login

You can configure an IdP-initiated login flow when configuring your IdP. The users then select the Sysdig application from your IdP’s app directory and do not need to browse directly to a Sysdig application URL.

See User and Team Administration for information on creating users.

Topics in This Section
Configure Google Cloud Authentication for OIDC

You can configure Google Cloud Authentication as an OpenID authentication mechanism in Sysdig. You may need to adjust the procedures based on the specifics of your environment.

Configure Okta for OIDC

You can configure Okta as an OpenID Connect (OIDC) authentication mechanism in Sysdig.

Configure OneLogin for OIDC

You can configure OneLogin as an OpenID authentication mechanism in Sysdig.

Configure Keycloak for OIDC

You can configure Keycloak as an OpenID authentication mechanism in Sysdig.

Configure Azure Active Directory for OIDC

OpenID Connect (OIDC) is a security-token based extension of the OAuth 2.0 authorization protocol to do single sign-on. Azure Active Directory (AD) provides an implementation of OIDC protocol and Sysdig supports it for single sign-on and API access to Sysdig application.