Tutorial: Configure Kisi Physical Security for automatic user provisioning

This tutorial describes the steps you need to do in both Kisi Physical Security and Azure Active Directory (Azure AD) to configure automatic user provisioning. When configured, Azure AD automatically provisions and de-provisions users and groups to Kisi Physical Security using the Azure AD Provisioning service. For important details on what this service does, how it works, and frequently asked questions, see Automate user provisioning and deprovisioning to SaaS applications with Azure Active Directory.

Capabilities Supported

  • Create users in Kisi Physical Security.
  • Remove users in Kisi Physical Security when they do not require access anymore.
  • Keep user attributes synchronized between Azure AD and Kisi Physical Security.
  • Provision groups and group memberships in Kisi Physical Security.
  • Single sign-on to Kisi Physical Security(recommended).

Prerequisites

The scenario outlined in this tutorial assumes that you already have the following prerequisites:

Step 1. Plan your provisioning deployment

  1. Learn about how the provisioning service works.
  2. Determine who will be in scope for provisioning.
  3. Determine what data to map between Azure AD and Kisi Physical Security.

Step 2. Configure Kisi Physical Security to support provisioning with Azure AD

Generate Secret Token in Kisi

  • Sign in to your Kisi Organization account

  • Under Organization Setup, click on SSO & SCIM

  • Toggle On Enable SCIM and click on Generate Token

    Secret Token

  • Copy the Token (this Token is only shown once)

Add Kisi Physical Security from the Azure AD application gallery to start managing provisioning to Kisi Physical Security. If you have previously setup Kisi Physical Security for SSO, you can use the same application. However it's recommended that you create a separate app when testing out the integration initially. Learn more about adding an application from the gallery here.

Step 4. Define who will be in scope for provisioning

The Azure AD provisioning service allows you to scope who will be provisioned based on assignment to the application and or based on attributes of the user / group. If you choose to scope who will be provisioned to your app based on assignment, you can use the following steps to assign users and groups to the application. If you choose to scope who will be provisioned based solely on attributes of the user or group, you can use a scoping filter as described here.

  • Start small. Test with a small set of users and groups before rolling out to everyone. When scope for provisioning is set to assigned users and groups, you can control this by assigning one or two users or groups to the app. When scope is set to all users and groups, you can specify an attribute based scoping filter.

  • If you need additional roles, you can update the application manifest to add new roles.

Step 5. Configure automatic user provisioning to Kisi Physical Security

This section guides you through the steps to configure the Azure AD provisioning service to create, update, and disable users and groups in Kisi Physical Security based on user and/or group assignments in Azure AD.

To configure automatic user provisioning for Kisi Physical Security in Azure AD:

  1. Sign in to the Azure portal. Select Enterprise Applications, then select All applications.

    Enterprise applications blade

  2. In the applications list, select Kisi Physical Security.

    The Kisi Physical Security link in the Applications list

  3. Select the Provisioning tab.

    Provisioning tab

  4. Set the Provisioning Mode to Automatic.

    Provisioning tab automatic

  5. In the Admin Credentials section, input your Kisi Physical Security Tenant URL and Secret Token provided by Kisi Physical Security. Click Test Connection to ensure Azure AD can connect to Kisi Physical Security. If the connection fails, contact Kisi Physical Security to check your account setup.

    Token

  6. In the Notification Email field, enter the email address of a person or group who should receive the provisioning error notifications and select the Send an email notification when a failure occurs check box.

    Notification Email

  7. Select Save.

  8. In the Mappings section, select Synchronize Azure Active Directory Users to Kisi Physical Security.

  9. Review the user attributes that are synchronized from Azure AD to Kisi Physical Security in the Attribute-Mapping section. The attributes selected as Matching properties are used to match the user accounts in Kisi Physical Security for update operations. If you choose to change the matching target attribute, you'll need to ensure that the Kisi Physical Security API supports filtering users based on that attribute. Select the Save button to commit any changes.

    Attribute Type Supported for filtering Required by Kisi Physical Security
    userName String
    active Boolean
    displayName String
    name.givenName String
    name.familyName String
    name.formatted String
  10. Under the Mappings section, select Synchronize Azure Active Directory Groups to Kisi Physical Security.

  11. Review the group attributes that are synchronized from Azure AD to Kisi Physical Security in the Attribute-Mapping section. The attributes selected as Matching properties are used to match the groups in Kisi Physical Security for update operations. Select the Save button to commit any changes.

    Attribute Type Supported for filtering Required by Kisi Physical Security
    displayName String
    members Reference
    externalId String
  12. To configure scoping filters, refer to the following instructions provided in the Scoping filter tutorial.

  13. To enable the Azure AD provisioning service for Kisi Physical Security, change the Provisioning Status to On in the Settings section.

    Provisioning Status Toggled On

  14. Define the users and groups that you would like to provision to Kisi Physical Security by choosing the appropriate values in Scope in the Settings section.

    Provisioning Scope

  15. When you're ready to provision, click Save.

    Saving Provisioning Configuration

This operation starts the initial synchronization cycle of all users and groups defined in Scope in the Settings section. The initial cycle takes longer to execute than next cycles, which occur approximately every 40 minutes as long as the Azure AD provisioning service is running.

Step 6. Monitor your deployment

Once you've configured provisioning, use the following resources to monitor your deployment:

  • Use the provisioning logs to determine which users have been provisioned successfully or unsuccessfully
  • Check the progress bar to see the status of the provisioning cycle and how close it's to completion
  • If the provisioning configuration seems to be in an unhealthy state, the application will go into quarantine. Learn more about quarantine states here.

More resources

Next steps