Verkada Account Provisioning using SCIM (Overview)
OVERVIEW
Verkada synchronizes with accounts from our local Active Directory Server using SCIM (System for Cross-Domain Identity Management) & SAML (Security Assertion Markup Language). The flow of information begins at the local AD and ends at the endpoint application (Verkada). Official documentation of the process and setup can be found in the link below, as well as the architecture of the configuration.
DATA FLOW
Verkada Sec Users (Account Group on Local AD) ----> M365 / Microsoft Entra ----> Verkada
Depending on your use case, Verkada Command has the ability to integrate with Microsoft Entra ID, amongst other Identify Providers [IdPs], in the following capacities:
Security Assertion Markup Language (SAML)
System for Cross-Domain Identity Management (SCIM)
SAML handles the authentication side of things allowing Microsoft Entra ID to be used to manage access to Command, the same as any other Software as a Service (SaaS) application already integrates into your Microsoft Entra ID tenant. This means that you can incorporate Command into your existing identity framework and authorize users based on your current policies.
SCIM allows you to leverage your existing users and groups already present in Microsoft Entra ID and synchronize these with Command. This allows you to retain the current central IdP, and configure permissions in Command using your existing users and groups.
Configuration
- Two Enterprise Apps (Entra Admin Center )