ANV085 Configuring SCIM in Brivo Eagle Eye Video Enhanced Web Interface

ANV085 Configuring SCIM in Brivo Eagle Eye Video Enhanced Web Interface

Application Note: Video - ANV085 

Configuring SCIM in Brivo Eagle Eye Video Enhanced Web Interface

2025-07-24 Revision 1.0


Target Audience


This application note is intended for Brivo Eagle Eye Video users and resellers managing customer accounts. SCIM 2.0 (System for Cross-domain Identity Management) provides a standardized way to automate user provisioning, updates, and de-provisioning between the Brivo Eagle Eye Video platform and external identity providers (IdPs) such as Microsoft Entra ID, Okta, and other SCIM-compliant systems.

Note: SCIM is not supported on reseller-level accounts; it is only supported on customer accounts.

Introduction


SCIM (System for Cross-domain Identity Management) is a standardized protocol designed to simplify and automate the management of user identities across cloud-based services. Integrating SCIM 2.0 with Brivo Eagle Eye Video provides a seamless way to automate user provisioning, updates, and de-provisioning between your IdP and Eagle Eye Networks Cloud VMS. This application note provides a step-by-step guide to enable SCIM 2.0 for your Brivo Eagle Eye Video account, including key configuration steps for popular IdPs like Okta and Microsoft Entra ID, formerly known as Azure Active Directory (Azure AD).

Prerequisites

Before enabling SCIM 2.0, ensure you have the following:

  1. Administrator Privileges: Access to Brivo Eagle Eye Video Admin settings.

  2. IdP Account: An account with a supported IdP like Okta or Microsoft Entra ID.

  3. API Key: You will generate this within the Brivo Eagle Eye Video Enhanced Web Interface.



Enable SCIM 2.0 


To enable SCIM 2.0 for your Brivo Eagle Eye Video account, follow the steps below based on your IdP setup (e.g., Okta, Microsoft Entra ID).

  • Brivo Eagle Eye Administrator Access: Ensure you have administrator privileges in the Brivo Eagle Eye Video.

  • Roles: To use the full benefits of SCIM, enable roles for users. Go to Admin > Account Settings > Defaults and check the Enable Roles for Users box under User Defaults.
    To learn more about Roles, see this application note: Simplify User Management with Eagle Eye Roles



  • Enable SCIM: To configure SCIM, first enable it under the Identity Provider tab. Go to Admin > Account Settings > Identity Provider and toggle the Enable SCIM button on and Save changes.






  • SCIM Base URL: The base URL for SCIM requests can be obtained from the Identity Provider tab within Account Settings. At the bottom of this window, see the Base URL:

  • SCIM API Key: The API key can be obtained from the Identity Provider tab within Account Settings. At the bottom of this window, enable SCIM, click Save Changes, then click Generate New API Key.

Configure SCIM 2.0 in Okta


This section provides detailed steps for configuring SCIM 2.0 in your Okta environment to seamlessly provision and manage users for your Brivo Eagle Eye Video account. You will learn how to create the SCIM enterprise application, enable provisioning, and manage attribute mappings.

Create the SCIM 2.0 Application

  1. Log in to the Okta Admin Console at https://admin.okta.com

  2. Go to Applications in the Okta admin console, then click Browse App Catalog to search for available integrations.

  3. Search for SCIM 2.0 Test App (OAuth Bearer Token) in the Okta app catalog, then click Add Integration to begin the setup.

  4. Click Add Integration to finalize and add the SCIM application to your environment.


  5. Enter a name for the application, then click Next to complete the integration setup.


Enable Provisioning for the New Application

  1. In the application, navigate to the Provisioning tab and click Configure API Integration to initiate the SCIM connection setup.

  1. Check Enable API Integration, then enter the Base URL and retrieve the API Key from the Eagle Eye Networks SCIM settings.

  2. Click Test API Credentials to verify the connection. 

  3. If successful, click Save to apply the configuration.


Update the Provisioning Configuration

  1. Go to the Provisioning tab, then select To App and click Edit to configure the provisioning settings. 






  1. Check Enable for Create Users, Update User Attributes, and Deactivate Users.

















  1. In the Attribute Mappings section, remove any unused or unsupported attributes.


Ensure the email and emailType attributes apply only on Create. For emailType, use the expression: "work".


  1. Next, go to the Sign On tab and click Edit to modify the sign-on settings for the application.


  2. Set the Application Username Format to Email, then click Save to apply the setting.

This ensures the user’s email is used as the unique identifier in Eagle Eye Networks.


Start Provisioning Users’ Okta


Note: Okta recommends using separate groups for App Assignment and Group Push.

If the same group is used for both, and a user is removed from that group (leaving no app assignment), Okta will only disable the user’s access to the application. In this case, no SCIM request is sent to remove the user from groups on the target application (Eagle Eye Networks).


  1. Use the Assignments section of the application to assign users and groups to the SCIM integration.

  2. Use the Assign button to add new users or groups to the application.



Start Provisioning Okta Groups 

  1. Use the Push Groups section to provision groups to the Eagle Eye Networks (EEN) account.






  1. In the Push Groups section, search for the group by name (e.g., EEN Group), select it, and save it to start syncing group membership to the EEN app.

  1. The group and its members will now be provisioned to the EEN application.

Note: Before linking an existing group from EEN to a group in Okta, click Refresh App Groups in Okta to fetch the latest groups from the EEN system. This ensures the correct group mapping and prevents sync issues.













Configuring SCIM 2.0 in Entra ID


This section provides detailed steps to configure SCIM 2.0 in your Azure Entra ID environment to seamlessly provision and manage users for your Brivo Eagle Eye Video account. You will learn how to create the SCIM enterprise application, enable provisioning, and manage attribute mappings.

  1. Log in to the Microsoft Entra ID admin portal: https://www.microsoft.com/en-us/security/business/identity-access/microsoft-entra-id

  2. Navigate to Enterprise Applications, then click + New Application to create a new SCIM integration.

  3. Select Create Your Own Application, enter a name for the app, and choose Integrate any Other Application You Don’t Find in the Gallery from the side panel. Then click Create.






Enable Provisioning for Entra ID


  1. After the app is created, navigate to the Provisioning section in the left-hand menu.


  1. Click on + New Configuration to begin setting up SCIM provisioning.




  1. Provide the Tenant URL (SCIM BaseUrl) and Secret Token (API - Key).

  1. Click Test Connection to verify the settings. If successful, click Save to apply the configuration.







Update Attribute Mappings in Microsoft Entra ID


This section defines how user attributes from Microsoft Entra ID are mapped to the SCIM API for Eagle Eye Networks. Proper mapping ensures users are provisioned with the correct information (e.g., name, email, role).

  1. Navigate to the Attribute Mappings section to review and customize which user attributes are sent to Eagle Eye Networks.

  1. Click Provision Microsoft Entra ID Groups, then update the attribute mappings as shown below. Click Save to apply the changes.



  1. Click Provision Microsoft Entra ID Users. Update the attribute mappings as specified, and click Save to apply the changes.


  1. For the Active attribute, use Not([IsSoftDeleted]) as the expression. This ensures only users who are not soft-deleted in Entra ID are provisioned to Eagle Eye Networks.

  1. Ensure the required attributes are present. Make sure each user has the following attributes filled in Microsoft Entra ID before provisioning:

  • First name

  • Last name

  • Email

Refer to the example below to locate these fields in the user profile.


Start Provisioning Users and Groups in Entra ID

  1. In the left panel, navigate to Users and Groups, then click Add User/Group.

  2. Add users and groups for the application. Provisioning to Eagle Eye Networks may take a few minutes to complete.


  1. You can also use Provision on Demand to provision individual users to the Eagle Eye Networks VMS immediately. This is useful for testing or urgent user syncs.


SCIM Provisioning Log Locations (Entra ID & Okta)


Log access varies by IdP. Use the instructions below based on your configured provider:


For Microsoft Entra ID:

The Provisioning Logs section displays detailed records of all provisioning operations, including user creation, updates, group assignments, and any failures. Use this to verify successful syncs or troubleshoot issues during SCIM provisioning to Eagle Eye Networks.


For Okta

The View Logs option in the Okta SCIM application page allows you to monitor provisioning activity, including user creation, updates, group assignments, and any failures. Use this to verify successful syncs or troubleshoot provisioning issues from Okta to Eagle Eye Networks.


Access Management via IdP Groups


Assigning Roles, Sites, and Layouts to IdP Groups

To streamline access management, roles, sites, and layouts can be assigned to Identity Provider (IdP) groups. Each group, such as Facilities-Access, Austin-HQ, or Reception-Cameras, can be mapped to users via the IdP. Once users are synced, they automatically inherit the assigned access depending on their group membership. This approach ensures consistent and scalable user provisioning across environments.

To edit group settings (e.g., roles, sites, layouts), press the gear icon at the end of the row for the corresponding group. 


Assigning Roles to an IdP Group

To assign roles to an IdP group, click the Roles tab in the group settings. If no roles have been assigned, click Assign roles +. A list of available roles will appear. Use the filter to search by name. Select the desired role(s) and click Save changes to complete the assignment.



Once a role is assigned to an IdP group, you can manage it via the Roles tab. Use the Manage Roles button to update assignments, filter roles by name, or click the trash icon to remove a role from the group.

Assigning Sites to an IdP Group

To assign sites to an IdP group, click the Sites tab in the group settings. If no sites are assigned yet, click Assign Sites +. A list of available sites will appear; use the filter to search by name. Select the desired site(s), then click Save Changes to complete the assignment.


Once a site is assigned to an IdP group, you can manage it via the Sites tab. Use the Manage Sites button to update assignments, filter sites by name, or click the trash icon to remove a site from the group.




Assigning Layouts to an IdP Group

To assign layouts to an IdP group, click the Layouts tab in the group settings. If no layouts are assigned yet, click Assign Layouts +. A list of available layouts will appear; use the filter to search by name. Select the desired layout(s), then click Save Changes to complete the assignment.


Once a layout is assigned to an IdP group, you can manage it via the Layouts tab. Use the Manage Layouts button to update assignments, filter layouts by name, or click the trash icon to remove a layout from the group.





Enable Access Management via IdP Group

To enable access management via IdP groups, ensure each group is assigned at least one Role, Site, or Layout. This ensures that users receive the correct access permissions when provisioned through your Identity Provider. Access management via IdP groups will take effect only after the enablement of “Roles management via IdP Groups” and/or “Sites and Layouts management via IdP Groups”.  

You can find this setting on the Identity Provider page in Account Settings.


Disabling SCM


If you disable SCIM integration, syncing with your Identity Provider will stop. All SCIM-managed users will be converted to regular users. Existing users will keep their current access, but all IdP Groups and related role, site, and layout assignments will be removed. Future updates from your IdP will no longer be applied.



Conclusion


This guide has walked you through configuring SCIM 2.0 (System for Cross-domain Identity Management) for your Brivo Eagle Eye Video account, including step-by-step instructions for integrating with popular Identity Providers (IdPs) like Okta and Microsoft Entra ID (formerly Azure Active Directory).

The configuration process included:

  • Setting up your Identity Provider

  • Enabling SCIM integration in your Eagle Eye account

  • Assigning roles, sites, and layouts to IdP groups

  • Testing and verifying user synchronization

By following these steps, your organization can automate key aspects of user lifecycle management:

  • Provisioning – Automatically create user accounts when employees join or require access

  • Updates – Keep roles, permissions, and user attributes synchronized in real time

  • De-provisioning – Securely deactivate accounts when access is no longer needed, minimizing the risk of stale or orphaned accounts

Implementing SCIM 2.0 enhances security by centralizing identity management and reducing human error. It also improves operational efficiency by automating manual, time-consuming user management tasks. This results in a more secure, efficient, and scalable Eagle Eye Networks Cloud VMS.