Configure the Pinniped Supervisor to use Okta as an OIDC provider
The Supervisor is an OpenID Connect (OIDC) issuer that supports connecting a single “upstream” identity provider to many “downstream” cluster clients.
This guide shows you how to configure the Supervisor so that users can authenticate to their Kubernetes cluster using their Okta credentials.
This how-to guide assumes that you have already installed the Pinniped Supervisor with working ingress, and that you have configured a FederationDomain to issue tokens for your downstream clusters.
Create an Okta Application
Follow the instructions for setting up an app using authcode flow and create an app. Optionally follow the instructions for customizing tokens returned from Okta with a groups claim if you want to pass users' Okta group information through to your Kubernetes clusters.
For example, to create an app:
- In the Okta Admin Console, navigate to Applications > Applications.
- Create a new app:
Create App Integration.
Sign-on method, select
Application type, app
Web Application, then click next.
- Enter a name for your app, such as “My Kubernetes Clusters”.
- Enter the sign-in redirect URI. This is the
spec.issueryou configured in your
- Optionally select
Limit access to selected groupsto restrict which Okta users can log in to Kubernetes using this integration.
- Save the app and make note of the Client ID and Client secret.
- Navigate to the Sign On tab > OpenID Connect ID Token and click
Edit. Fill in the Groups claim filter. For example, for all groups to be present under the claim name
groups, fill in “groups” in the first box, then select “Matches regex” and “.*”.
Configure the Supervisor
Create an OIDCIdentityProvider in the same namespace as the Supervisor.
For example, this OIDCIdentityProvider and corresponding Secret use Okta’s
apiVersion: idp.supervisor.pinniped.dev/v1alpha1 kind: OIDCIdentityProvider metadata: namespace: pinniped-supervisor name: okta spec: # Specify the upstream issuer URL (no trailing slash). issuer: https://my-company.okta.com # Request any scopes other than "openid" for claims besides # the default claims in your token. The "openid" scope is always # included. # # To learn more about how to customize the claims returned, see here: # https://developer.okta.com/docs/guides/customize-tokens-returned-from-okta/overview/ authorizationConfig: additionalScopes: [groups, email] # Specify how Okta claims are mapped to Kubernetes identities. claims: # Specify the name of the claim in your Okta token that will be mapped # to the "username" claim in downstream tokens minted by the Supervisor. username: email # Specify the name of the claim in Okta that represents the groups # that the user belongs to. This matches what you specified above # with the Groups claim filter. groups: groups # Specify the name of the Kubernetes Secret that contains your Okta # application's client credentials (created below). client: secretName: okta-client-credentials --- apiVersion: v1 kind: Secret metadata: namespace: pinniped-supervisor name: okta-client-credentials type: secrets.pinniped.dev/oidc-client stringData: # The "Client ID" that you got from Okta. clientID: "<your-client-id>" # The "Client secret" that you got from Okta. clientSecret: "<your-client-secret>"
Once your OIDCIdentityProvider has been created, you can validate your configuration by running:
kubectl describe OIDCIdentityProvider -n pinniped-supervisor okta
Look at the
status field. If it was configured correctly, you should see
Next, configure the Concierge to validate JWTs issued by the Supervisor! Then you’ll be able to log into those clusters as any of the users from the Okta directory.