How To Integrate Ping Identity SSO with Chainguard

The Chainguard platform supports Single sign-on (SSO) authentication for users. By default, users can log in with GitHub, GitLab and Google, but SSO support allows users to bring their own identity provider for authentication.

This guide outlines how to create a Ping Identity Application and integrate it with Chainguard. After completing this guide, you’ll be able to log in to Chainguard using Ping and will no longer be limited to the default SSO options.

Prerequisites

To complete this guide, you will need the following.

• chainctl installed on your system. Follow our guide on How To Install chainctl if you don’t already have this installed.
• A Ping Identity account over which you have administrative access.
• A Custom IDP quota of at least 1. You can reach out to Chainguard’s support team for help with this.

Create a Ping Identity Application

To integrate the Ping identity provider with the Chainguard platform, sign on to Ping Identity and navigate to the Dashboard. Click on the Connections tab in the left hand sidebar menu, and then click on Applications in the resulting dropdown menu. From the Applications landing page, click the plus sign (➕) to set up a new application.

Configure the application as follows:

• Application Name: Set a name and option description (such as “Chainguard”) to ensure users recognize this application is for authentication to the Chainguard platform.
• Icon: You can optionally add a Chainguard logo icon here to help your users visually identify this integration. If you’d like, you can use the icon from the Chainguard Console.
• Application Type: Select OIDC Web App.

After setting these details, click the Save button.

Next, configure scopes for the application. In the Overview tab, click the Resource Access scope button.

Add email and profile scopes, then save.

Next, configure the OIDC application. Navigate to the Configuration tab and click the “edit” icon.

To configure the application, add the following settings.

• Response Type: Select the Code checkbox.
• Grant Type: Select the Authorization Code checkbox, and set PKCE Enforcement to “Optional.”

Warning: Setting a grant type other than Authorization Code may compromise your security posture.

• Redirect URIs: Set the Redirect URI to https://issuer.enforce.dev/oauth/callback.

Click the Save button to save your configuration.

Finally, enable the Chainguard application by toggling the knob in the top right corner.

This completes configuration of the Ping application. You’re now ready to configure the Chainguard platform to use it.

Configuring Chainguard to use Ping SSO

Now that your Okta application is ready, you can create the custom identity provider.

First, log in to Chainguard with chainctl, using an OIDC provider like Google, GitHub, or GitLab to bootstrap your account.

chainctl auth login

Note that this bootstrap account can be used as a backup account (that is, a backup account you can use to log in if you ever lose access to your primary account). However, if you prefer to remove this role-binding after configuring the custom IDP, you may also do so.

To configure Chainguard make a note of the following settings from your Ping application. These can be found in the Ping console under the Configuration tab of the Application page.

• Client ID
• Client Secret
• Issuer URL

You will also need the UIDP for the Chainguard organization under which you want to install the identity provider. Your selection won’t affect how your users authenticate but will have implications on who has permission to modify the SSO configuration.

You can retrieve a list of all the Chainguard organizations you belong to — along with their UIDPs — with the following command.

chainctl iam organizations ls -o table

                         	ID                         	|  	  NAME    |	DESCRIPTION
--------------------------------------------------------+-------------+---------------------
  59156e77fb23e1e5ebcb1bd9c5edae471dd85c43              | sample_org  |
  . . .                                                 | . . .       |

Note down the ID value for your chosen organization.

With this information in hand, create a new identity provider with the following commands.

export NAME=ping-id
export CLIENT_ID=<your client id here>
export CLIENT_SECRET=<your client secret here>
export ISSUER=<your issuer url here>
export ORG=<your organization UIDP here>
chainctl iam identity-provider create \
  --configuration-type=OIDC \
  --oidc-client-id=${CLIENT_ID} \
  --oidc-client-secret=${CLIENT_SECRET} \
  --oidc-issuer=${ISSUER} \
  --oidc-additional-scopes=email \
  --oidc-additional-scopes=profile \
  --parent=${ORG} \
  --default-role=viewer \
  --name=${NAME}

Note the --default-role option. This defines the default role granted to users registering with this identity provider. This example specifies the viewer role, but depending on your needs you might choose editor or owner. If you don’t include this option, you’ll be prompted to specify the role interactively. For more information, refer to the IAM and Security section of our Introduction to Custom Identity Providers in Chainguard tutorial.

You can refer to our Generic Integration Guide in our Introduction to Custom Identity Providers guide for more information about the chainctl iam identity-provider create command and its required options.