|
| 1 | +--- |
| 2 | +title: 'Tutorial: Configure Kisi Physical Security for automatic user provisioning with Azure Active Directory | Microsoft Docs' |
| 3 | +description: Learn how to automatically provision and de-provision user accounts from Azure AD to Kisi Physical Security. |
| 4 | +services: active-directory |
| 5 | +author: twimmers |
| 6 | +writer: twimmers |
| 7 | +manager: beatrizd |
| 8 | + |
| 9 | +ms.assetid: 2d4840ae-146d-4649-aaf1-5efe35abbd51 |
| 10 | +ms.service: active-directory |
| 11 | +ms.subservice: saas-app-tutorial |
| 12 | +ms.workload: identity |
| 13 | +ms.topic: tutorial |
| 14 | +ms.date: 11/01/2021 |
| 15 | +ms.author: thwimmer |
| 16 | +--- |
| 17 | + |
| 18 | +# Tutorial: Configure Kisi Physical Security for automatic user provisioning |
| 19 | + |
| 20 | +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](https://www.getkisi.com/) 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](../app-provisioning/user-provisioning.md). |
| 21 | + |
| 22 | + |
| 23 | +## Capabilities Supported |
| 24 | +> [!div class="checklist"] |
| 25 | +> * Create users in Kisi Physical Security. |
| 26 | +> * Remove users in Kisi Physical Security when they do not require access anymore. |
| 27 | +> * Keep user attributes synchronized between Azure AD and Kisi Physical Security. |
| 28 | +> * Provision groups and group memberships in Kisi Physical Security. |
| 29 | +> * [Single sign-on](kisi-physical-security-tutorial.md) to Kisi Physical Security(recommended). |
| 30 | +
|
| 31 | +## Prerequisites |
| 32 | + |
| 33 | +The scenario outlined in this tutorial assumes that you already have the following prerequisites: |
| 34 | + |
| 35 | +* [An Azure AD tenant](../develop/quickstart-create-new-tenant.md). |
| 36 | +* A user account in Azure AD with [permission](../roles/permissions-reference.md) to configure provisioning (for example, Application Administrator, Cloud Application administrator, Application Owner, or Global Administrator). |
| 37 | +* A [Kisi Organization license](https://www.getkisi.com/enterprise) |
| 38 | + |
| 39 | +## Step 1. Plan your provisioning deployment |
| 40 | +1. Learn about [how the provisioning service works](../app-provisioning/user-provisioning.md). |
| 41 | +1. Determine who will be in [scope for provisioning](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md). |
| 42 | +1. Determine what data to [map between Azure AD and Kisi Physical Security](../app-provisioning/customize-application-attributes.md). |
| 43 | + |
| 44 | +## Step 2. Configure Kisi Physical Security to support provisioning with Azure AD |
| 45 | + |
| 46 | +### Generate Secret Token in Kisi |
| 47 | + |
| 48 | +* Sign in to your Kisi Organization account |
| 49 | + |
| 50 | +* Under Organization Setup, click on SSO & SCIM |
| 51 | + |
| 52 | +* Toggle On Enable SCIM and click on Generate Token |
| 53 | + |
| 54 | +  |
| 55 | + |
| 56 | +* Copy the Token (this Token is only shown once) |
| 57 | + |
| 58 | +## Step 3. Add Kisi Physical Security from the Azure AD application gallery |
| 59 | + |
| 60 | +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](../manage-apps/add-application-portal.md). |
| 61 | + |
| 62 | +## Step 4. Define who will be in scope for provisioning |
| 63 | + |
| 64 | +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](../manage-apps/assign-user-or-group-access-portal.md) 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](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md). |
| 65 | + |
| 66 | +* When assigning users and groups to Kisi Physical Security, you must select a role other than **Default Access**. Users with the Default Access role are excluded from provisioning and will be marked as not effectively entitled in the provisioning logs. If the only role available on the application is the default access role, you can [update the application manifest](../develop/howto-add-app-roles-in-azure-ad-apps.md) to add more roles. |
| 67 | + |
| 68 | +* 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](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md). |
| 69 | + |
| 70 | + |
| 71 | +## Step 5. Configure automatic user provisioning to Kisi Physical Security |
| 72 | + |
| 73 | +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. |
| 74 | + |
| 75 | +### To configure automatic user provisioning for Kisi Physical Security in Azure AD: |
| 76 | + |
| 77 | +1. Sign in to the [Azure portal](https://portal.azure.com). Select **Enterprise Applications**, then select **All applications**. |
| 78 | + |
| 79 | +  |
| 80 | + |
| 81 | +1. In the applications list, select **Kisi Physical Security**. |
| 82 | + |
| 83 | +  |
| 84 | + |
| 85 | +1. Select the **Provisioning** tab. |
| 86 | + |
| 87 | +  |
| 88 | + |
| 89 | +1. Set the **Provisioning Mode** to **Automatic**. |
| 90 | + |
| 91 | +  |
| 92 | + |
| 93 | +1. 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. |
| 94 | + |
| 95 | +  |
| 96 | + |
| 97 | +1. 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. |
| 98 | + |
| 99 | +  |
| 100 | + |
| 101 | +1. Select **Save**. |
| 102 | + |
| 103 | +1. In the **Mappings** section, select **Synchronize Azure Active Directory Users to Kisi Physical Security**. |
| 104 | + |
| 105 | +1. 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](../app-provisioning/customize-application-attributes.md), 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. |
| 106 | + |
| 107 | + |Attribute|Type|Supported for filtering|Required by Kisi Physical Security| |
| 108 | + |---|---|---|---| |
| 109 | + |userName|String|✓|✓| |
| 110 | + |active|Boolean||| |
| 111 | + |displayName|String||| |
| 112 | + |name.givenName|String||| |
| 113 | + |name.familyName|String||| |
| 114 | + |name.formatted|String||| |
| 115 | + |
| 116 | + |
| 117 | +1. Under the **Mappings** section, select **Synchronize Azure Active Directory Groups to Kisi Physical Security**. |
| 118 | + |
| 119 | +1. 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. |
| 120 | + |
| 121 | + |Attribute|Type|Supported for filtering|Required by Kisi Physical Security| |
| 122 | + |---|---|---|---| |
| 123 | + |displayName|String|✓|✓ |
| 124 | + |members|Reference|| |
| 125 | + |externalId|String||| |
| 126 | +1. To configure scoping filters, refer to the following instructions provided in the [Scoping filter tutorial](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md). |
| 127 | + |
| 128 | +1. To enable the Azure AD provisioning service for Kisi Physical Security, change the **Provisioning Status** to **On** in the **Settings** section. |
| 129 | + |
| 130 | +  |
| 131 | + |
| 132 | +1. 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. |
| 133 | + |
| 134 | +  |
| 135 | + |
| 136 | +1. When you're ready to provision, click **Save**. |
| 137 | + |
| 138 | +  |
| 139 | + |
| 140 | +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. |
| 141 | + |
| 142 | +## Step 6. Monitor your deployment |
| 143 | +Once you've configured provisioning, use the following resources to monitor your deployment: |
| 144 | + |
| 145 | +* Use the [provisioning logs](../reports-monitoring/concept-provisioning-logs.md) to determine which users have been provisioned successfully or unsuccessfully |
| 146 | +* Check the [progress bar](../app-provisioning/application-provisioning-when-will-provisioning-finish-specific-user.md) to see the status of the provisioning cycle and how close it's to completion |
| 147 | +* If the provisioning configuration seems to be in an unhealthy state, the application will go into quarantine. Learn more about quarantine states [here](../app-provisioning/application-provisioning-quarantine-status.md). |
| 148 | + |
| 149 | +## More resources |
| 150 | + |
| 151 | +* [Managing user account provisioning for Enterprise Apps](../app-provisioning/configure-automatic-user-provisioning-portal.md) |
| 152 | +* [What is application access and single sign-on with Azure Active Directory?](../manage-apps/what-is-single-sign-on.md) |
| 153 | + |
| 154 | +## Next steps |
| 155 | + |
| 156 | +* [Learn how to review logs and get reports on provisioning activity](../app-provisioning/check-status-user-account-provisioning.md) |
0 commit comments