An organization's System for Cross-Domain Identity Management (SCIM) token authenticates Azure Active Directory (AD) or Okta to dynamically provision users and groups in Verkada Command.
Generate a SCIM token
In Verkada Command, go to All Products > Admin page.
Select Privacy & Security > SCIM Configuration to manage the SCIM configuration.
Click Add Domain and enter the desired email domains.
(Optional) Toggle off Send Email Invites if you do not want users to receive an email invite when their account is created.
The newly generated SCIM token displays.
Select the token to copy it to your clipboard.
⚠️ Immediately update your Azure AD or Okta configuration with this new token. Once the page is reloaded, the token does not re-appear.
Refresh a SCIM token
If you want to regenerate this token, such as if it is lost or compromised, you can do this in Command.
Once you refresh an organization's SCIM token, the previous token is immediately invalidated. As such, you should immediately copy the new token into Azure AD or Okta to ensure there is no interruption to your user provisioning.
Requirements
Your organization must already have had SCIM provisioning enabled.
You must be an Organization Admin (Org Admin) to refresh the SCIM token.
How it works
In Command, go to All Products > Admin.
Select Privacy & Security > SCIM Configuration.
Click Refresh.
When the warning message displays, click Continue to confirm.
The newly generated SCIM token displays.Select the token to copy it to your clipboard. This new token revokes the previous one and cannot be undone. You should see a notification that your new token has been successfully generated.
⚠️ Immediately update your Azure AD or Okta configuration with this new token. Once the page is reloaded, the token does not re-appear.
Need more help? Contact Verkada Support.