Skip to content

Update SCIM provisioning requirements in documentation #11844

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
lorenyeung wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Update SCIM provisioning requirements in documentation #11844

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f0d95e2
Update SCIM provisioning requirements in documentation
lorenyeung Mar 10, 2026
7973e85
Update SCIM provisioning instructions for clarity
lorenyeung Mar 10, 2026
d8cc720
Update provision-users-with-okta-scim.md
lorenyeung Mar 10, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions ...orm/role-based-access-control/provision-users-and-groups-using-azure-ad-scim.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,9 +24,9 @@ You need an understanding of:
* [Harness' key concepts](/docs/platform/get-started/key-concepts.md).
* [RBAC in Harness](/docs/platform/role-based-access-control/rbac-in-harness).

You must be an Administrator in your Microsoft Entra ID account, and you must be an **Account Admin** in Harness.
You must be an Administrator in your Microsoft Entra ID account, and you must have atleast the permissions to 'manage' and 'create/edit' account level service accounts and 'create/edit' account roles in Harness in order to perform all the steps necessary to provide an API key to Entra for provisioning. Generally, the steps below are handled by a Harness Admin.

You need a Harness [API key and unexpired token](/docs/platform/automation/api/add-and-manage-api-keys) that has all **Users** and **User Groups** [permissions](/docs/platform/automation/api/api-permissions-reference). API keys inherit permissions from the user they are associated with. If you use an API key for a [service account](./add-and-manage-service-account.md), make sure the service account has all **Users** and **User Groups** permissions.
You need to create a Harness [API key and unexpired token](/docs/platform/automation/api/add-and-manage-api-keys) that has all (view+manage+invite) **Users** and **User Groups** [permissions](/docs/platform/automation/api/api-permissions-reference). API keys inherit permissions from the user they are associated with. It is recommended that a separate service account is created for SCIM. Similar to a user API key, if you create an API key for a [service account](./add-and-manage-service-account.md), make sure the service account is binded with a role containg all (view+manage+invite) **Users** and **User Groups** permissions.

## Add Harness in Microsoft Entra ID

Expand Down
4 changes: 2 additions & 2 deletions ...orm/role-based-access-control/provision-users-and-groups-with-one-login-scim.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,9 +30,9 @@ You need an understanding of:
* [Harness' key concepts](/docs/platform/get-started/key-concepts.md).
* [RBAC in Harness](/docs/platform/role-based-access-control/rbac-in-harness).

You must be an Administrator in your OneLogin account, and you must be an **Account Admin** in Harness.
You must be an Administrator in your OneLogin account, and you must have atleast the permissions to 'manage' and 'create/edit' account level service accounts and 'create/edit' account roles in Harness in order to perform all the steps necessary to provide an API key to Entra for provisioning. Generally, the steps below are handled by a Harness Admin.

You need a Harness [API key and unexpired token](/docs/platform/automation/api/add-and-manage-api-keys) that has all **Users** and **User Groups** [permissions](/docs/platform/automation/api/api-permissions-reference). API keys inherit permissions from the user they are associated with. If you use an API key for a [service account](./add-and-manage-service-account.md), make sure the service account has all **Users** and **User Groups** permissions.
You need to create a Harness [API key and unexpired token](/docs/platform/automation/api/add-and-manage-api-keys) that has all (view+manage+invite) **Users** and **User Groups** [permissions](/docs/platform/automation/api/api-permissions-reference). API keys inherit permissions from the user they are associated with. It is recommended that a separate service account is created for SCIM. Similar to a user API key, if you create an API key for a [service account](./add-and-manage-service-account.md), make sure the service account is binded with a role containg all (view+manage+invite) **Users** and **User Groups** permissions.

## Add the Harness app to OneLogin

Expand Down
4 changes: 2 additions & 2 deletions docs/platform/role-based-access-control/provision-users-with-okta-scim.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,9 +24,9 @@ You need an understanding of:
* [Harness' key concepts](/docs/platform/get-started/key-concepts.md).
* [RBAC in Harness](/docs/platform/role-based-access-control/rbac-in-harness).

You must be an Administrator in your Okta account, and you must be an **Account Admin** in Harness.
You must be an Administrator in your Okta account, and you must have atleast the permissions to 'manage' and 'create/edit' account level service accounts and 'create/edit' account roles in Harness in order to perform all the steps necessary to provide an API key to Entra for provisioning. Generally, the steps below are handled by a Harness Admin.

You need a Harness [API key and unexpired token](/docs/platform/automation/api/add-and-manage-api-keys) that has all **Users** and **User Groups** [permissions](/docs/platform/automation/api/api-permissions-reference). API keys inherit permissions from the user they are associated with. If you use an API key for a [service account](./add-and-manage-service-account.md), make sure the service account has all **Users** and **User Groups** permissions.
You need to create a Harness [API key and unexpired token](/docs/platform/automation/api/add-and-manage-api-keys) that has all (view+manage+invite) **Users** and **User Groups** [permissions](/docs/platform/automation/api/api-permissions-reference). API keys inherit permissions from the user they are associated with. It is recommended that a separate service account is created for SCIM. Similar to a user API key, if you create an API key for a [service account](./add-and-manage-service-account.md), make sure the service account is binded with a role containg all (view+manage+invite) **Users** and **User Groups** permissions.

## Create an Okta app integration

Expand Down