Before you begin

Configure Single Sign-On OIDC

Verkada currently only supports Okta and Microsoft Entra ID (Azure AD) identity providers for Single Sign-On with OIDC. For a detailed setup guide, refer to OIDC based SSO for Okta.

OIDC SSO must be enabled in your organization to enable ECE.

Update Command mobile app

To ensure a smooth user experience, ask all users in your organization to update their Verkada Command mobile app. The app updates automatically unless auto-update is disabled. This step is required only for users of the Command mobile app.

iOS: Verkada Command
Android: Verkada Command

There is no need to update the Verkada Pass app.

Enable ECE

In Verkada Command, go to All Products > Admin.
In the left navigation, select Privacy & Security > Enterprise Controlled Encryption.
Click Get Started.
Under Generate Key:
1. Click Generate Key
2. Download the encryption key.
3. Add the encryption key to your identity provider.
4. Click Continue.
Under Verify:
1. Click Logout and Test.
2. If the test is successful, you will be redirected to this page.
3. Click Continue.
Under Enroll Devices:
1. Click Select Devices and choose the devices to enroll in ECE.
  Note: We recommend choosing Select All Devices to ensure you have the additional security and data protection for your entire fleet.
2. Click Enroll Devices.

Example template of the encryption key file:

File name: <command-org-name>_org_secret.txt 

Format:
<display-name / variable-name>

<encryption-key>

Add Encryption Key to Identity Provider

ECE is currently only supported on Okta and Microsoft Entra ID (Azure AD). Follow the steps below based on your identity provider.

Okta

Log in your Okta admin account.
On the left, click Directory.
Click Profile Editor.
Open Verkada SSO OIDC User.
Select Add Attribute.
1. Add the Display name and Variable name (both values are the same) from the “<org_name>_org_secret.txt” file. It starts with “vkdae2ee…”.
2. Click Save.
Select Mappings.
1. Click Okta User to Verkada SSO OIDC.
2. Copy the <encryption-key> value (the second value) in the downloaded “<org_name>_org_secret.txt” file (including the quotation marks).
3. At the bottom of the Mappings page, paste the <encryption-key> into the text box corresponding to the new variable just added above.
4. Click on the icon in the middle between the <encryption-key> and <variable-name>, and select Apply mapping on user create and update.
5. Click Save Mappings then Apply updates now.

Refer to Add Custom Profile Attributes if you run into issues editing the profile.

Microsoft Entra ID (Azure AD)

Log in to your Azure portal.
Search for and select App registrations.
Select Verkada SSO OIDC.
Note: If you do not see this app, go to All applications.
On the left, click Manage > App roles.
1. Click Create app role.
2. Add the Display name and Description (both values are the same) from the “<org_name>_org_secret.txt” file. It starts with “vkdae2ee…”.
3. Under Allowed member types select Users/Groups.
4. Under Value enter <display-name>:<encryption-key> (second value) in the downloaded “<org_name>_org_secret.txt” file. Do not copy the quotes for the encryption key.
5. Click Apply.
On the left, click on Manage Token > Configuration.
1. Click Add groups claim.
2. Select Security groups as the group type.
3. Select Emit groups as role claims as the ID.
4. Click Add.
On the left side, click on Manage > Authentication.
1. Under Implicit grant and hybrid flows, select both ID tokens and Access tokens.
2. Click Save.
On the left, click on Manage > Manifest.
1. Verify Manifest for Optional Claims looks like this:
  Note: You must see idToken.additionalProperties.emit_as_roles.
Assign the users to the new role. Only these users will be able to access Verkada Command.
1. Search for and select Microsoft Entra ID.
2. On the left, click Manage > Enterprise applications.

Need more help? Contact Verkada Support.

Okta SAML Integration

Okta SCIM Integration

Quick Reference Guide for Verkada Command

OIDC based SSO for Okta

Remove Enterprise Controlled Encryption