Skip to main content

Use the Setting API to enable SCIM API authentication through JWT

You can use JSON Web Tokens (JWT) for authentication with Harness SCIM APIs. To do this, you use the Harness Setting API to configure the settings corresponding to JWT.


Prepare the service account

A Harness service account is necessary to authorize access to the API. The service account must have these permissions:

  • Users: View, Manage, and Invite.
  • User groups: View and Manage.

You can create a new service account or use an existing one. For more information, go to Manage service accounts.

To create a service account:

  1. In Harness, select Account Settings, and then select Access Control.

  2. Select Service Accounts in the header, and then select New Service Account.

  3. Enter a Name and Email for the service account.

  4. Make note of the Id that is generated based on the Name. You need the Id to Enable JWT authentication.

  5. Select Save.

  6. Select Manage Roles next to the new service account and select a role and resource group that provide the following permissions:

    • Users: View, Manage, and Invite.
    • User groups: View and Manage.

    For more information on roles, resource groups, and permissions, go to RBAC in Harness.

Enable JWT authentication

The following curl command to send a request to the Setting API to update the settings required to enable JWT authentication. To use this command:

  • Replace SERVICE_ACCOUNT_ID with the ID for your Harness service account.
  • Replace ACCOUNT_ID with your Harness account ID.
  • Replace API_KEY_TOKEN with your personal access token.
  • Replace KEY_FIELD_VALUE with the identifier for a field corresponding to the JWT claims map.
  • Replace VALUE_FIELD_VALUE with the value corresponding with the key field.
  • Replace JWT_KEYS_URL_VALUE with the endpoint for the JWT keys JSON data.
        curl --location --request PUT '' \
--header 'Connection: keep-alive' \
--header 'x-api-key: API_KEY_TOKEN' \
--header 'Accept: */*' \
--header 'Accept-Language: en-US,en;q=0.9' \
--header 'Content-Type: application/json' \
--data-raw '[
"identifier": "scim_jwt_token_jwks_keys_url",
"value": "JWT_KEYS_URL_VALUE",
"allowOverrides": false,
"updateType": "UPDATE"
"identifier": "scim_jwt_token_key_field",
"value": "KEY_FIELD_VALUE",
"allowOverrides": false,
"updateType": "UPDATE"
"identifier": "scim_jwt_token_value_field",
"allowOverrides": false,
"updateType": "UPDATE"
"identifier": "scim_jwt_token_service_account_id",
"allowOverrides": false,
"updateType": "UPDATE"

Settings take effect 120 seconds after a successful request.

Use a JWT for Harness SCIM API authentication


Currently, this feature is behind the feature flag PL_SUPPORT_JWT_TOKEN_SCIM_API. Contact Harness Support to enable the feature.

You can access the Harness SCIM API by using JSON Web Tokens (JWT). This allows you to use email addresses, other than the ones you have registered with Harness, for IdP authentication. After successful authentication, you can use a JWT to invoke the Harness SCIM APIs.

  1. Make sure you have permission to Manage and View users and user groups.
  2. Enable JWT authentication.
  3. Use your JWT in Bearer headers in SCIM API requests, such as --header 'Authorization: Bearer JWT_TOKEN'.

For example, the following curl command fetches a list of all users in your Harness account, and it uses the JWT for authentication. To use this command, you must replace JWT_TOKEN in the Bearer header with your JWT, and you need to replace ACCOUNT_ID with your Harness account ID.

  curl --location --request GET '' \
--header 'Connection: keep-alive' \
--header 'Accept: application/scim+json' \
--header 'Authorization: Bearer JWT_TOKEN' \
--header 'Cookie: _cfuvid=CO...88'

To complete authentication, Harness validates the following:

  • The authenticity of the issued JWT. To do this, Harness uses the public JWT keys URL specified when you enabled JWT authentication.
  • The claims in the JWT token. Harness matches the claims in the token to those defined in the account settings when you enabled JWT authentication.