authentik ​S​C​I​M ​Provisioning

Sync Users and Groups from authentik to Kestra using SCIM.

Prerequisites

• authentik Account: An account with administrative privileges to configure SCIM provisioning.
• Enable multi-tenancy in Kestra: Tenants must be enabled in Kestra to support SCIM provisioning. You can enable tenants by setting the kestra.ee.tenants.enabled configuration property to true:

kestra:
  ee:
    tenants:
      enabled: true

Kestra SCIM Setup: Create a New Provisioning Integration

1. In the Kestra UI, navigate to the Administration → IAM → Provisioning page.
2. Click on the Create button in the top right corner of the page.
3. Fill in the following fields:
   • Name: Enter a name for the provisioning integration.
   • Description: Provide a brief description of the integration.
   • Provisioning Type: Currently, only SCIM 2.0 is supported — leave the default selection and click Save.

The above steps will generate a SCIM endpoint URL and a Secret Token that you will use to authenticate authentik with the SCIM integration in Kestra. Save those details, as they will be needed in the next steps.

The endpoint should look as follows:

https://your_kestra_host/api/v1/your_tenant/integrations/integration_id/scim/v2

The Secret Token will be a long string (approximately 200 characters) used to authenticate requests from authentik to Kestra.

Enable or Disable SCIM Integration

Note that you can disable or completely remove the SCIM Integration at any time. When an integration is disabled, all incoming requests to that integration endpoint will be rejected.

IAM Role and Service Account

When creating a new Provisioning Integration, Kestra will automatically create two additional objects:

1. Role SCIMProvisioner with the following permissions:
   • GROUPS: CREATE, READ UPDATE, DELETE
   • USERS: CREATE, READ, UPDATE
   • BINDINGS: CREATE, READ, UPDATE, DELETE
2. Service Account with an API Token which was previously displayed as a Secret Token for the integration:

authentik SCIM 2.0 Setup

Configuring SCIM 2.0 follows a process similar to SSO — you'll need to create a new Application. Then, in the second step, select SCIM as the Provider Type.

In the Protocol settings section, enter the URL and Secret Token obtained from Kestra.

Test both SSO and SCIM by adding users and groups

First, create Users and Groups in the Directory settings.

Then assign your user(s) to an existing group.

You can set a password for each authentik user to allow them to log in directly to Kestra with their username/email and password.

Once groups and users are created, they should be visible in the Kestra UI under the IAM → Users and Groups sections. It’s best to log in as the default admin user and attach the desired Role to each group to ensure that the users have the necessary permissions.

Then, to verify access, log in as one of those new authentik users in a separate browser or incognito mode and verify that the user has the permissions you expect.

Additional Resources

• SCIM for authentik Documentation
• Manage applications in authentik Documentation