Skip to content

Commit 16580bb

Browse files
authored
Merge pull request #163596 from MicrosoftDocs/master
6/24 AM Publish
2 parents 54d8b97 + 95981a5 commit 16580bb

File tree

529 files changed

+2360
-17447
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

529 files changed

+2360
-17447
lines changed

.openpublishing.redirection.json

Lines changed: 374 additions & 73 deletions
Large diffs are not rendered by default.

articles/active-directory/develop/quickstart-v2-aspnet-webapp.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
2-
title: "Quickstart: Add sign-in with Microsoft to an ASP.NET web app | Azure"
2+
title: "Quickstart: ASP.NET web app that signs in users"
33
titleSuffix: Microsoft identity platform
4-
description: In this quickstart, learn how to implement Microsoft sign-in on an ASP.NET web app by using OpenID Connect.
4+
description: Download and run a code sample that shows how an ASP.NET web app can sign in Azure AD users.
55
services: active-directory
66
author: jmprieur
77
manager: CelesteDG
@@ -13,12 +13,12 @@ ms.workload: identity
1313
ms.date: 09/25/2020
1414
ms.author: jmprieur
1515
ms.custom: "devx-track-csharp, aaddev, identityplatformtop40, scenarios:getting-started, languages:ASP.NET, contperf-fy21q1"
16-
#Customer intent: As an application developer, I want to know how to write an ASP.NET web app that can sign in personal accounts, as well as work and school accounts, from any Azure Active Directory instance.
16+
# Customer intent: As an application developer, I want to see a sample ASP.NET web app that can sign in Azure AD users.
1717
---
1818

19-
# Quickstart: Add Microsoft identity platform sign-in to an ASP.NET web app
19+
# Quickstart: ASP.NET web app that signs in Azure AD users
2020

21-
In this quickstart, you download and run a code sample that demonstrates how an ASP.NET web app can sign in users from any Azure Active Directory (Azure AD) organization.
21+
In this quickstart, you download and run a code sample that demonstrates an ASP.NET web application that can sign in users with Azure Active Directory (Azure AD) accounts.
2222

2323
> [!div renderon="docs"]
2424
> The following diagram shows how the sample app works:
Lines changed: 163 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,163 @@
1+
---
2+
title: 'Tutorial: Configure CheckProof 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 CheckProof.
4+
services: active-directory
5+
documentationcenter: ''
6+
author: Zhchia
7+
writer: Zhchia
8+
manager: beatrizd
9+
10+
ms.assetid: b036510b-bf7a-4284-ac17-41a5b10e2b55
11+
ms.service: active-directory
12+
ms.subservice: saas-app-tutorial
13+
ms.workload: identity
14+
ms.tgt_pltfrm: na
15+
ms.devlang: na
16+
ms.topic: article
17+
ms.date: 06/21/2021
18+
ms.author: Zhchia
19+
---
20+
21+
# Tutorial: Configure CheckProof for automatic user provisioning
22+
23+
This tutorial describes the steps you need to perform in both CheckProof and Azure Active Directory (Azure AD) to configure automatic user provisioning. When configured, Azure AD automatically provisions and de-provisions users and groups to [CheckProof](https://checkproof.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](../manage-apps/user-provisioning.md).
24+
25+
26+
## Capabilities Supported
27+
> [!div class="checklist"]
28+
> * Create users in CheckProof
29+
> * Remove users in CheckProof when they do not require access anymore
30+
> * Keep user attributes synchronized between Azure AD and CheckProof
31+
> * Provision groups and group memberships in CheckProof
32+
> * [Single sign-on](https://docs.microsoft.com/azure/active-directory/saas-apps/checkproof-tutorial) to CheckProof (recommended)
33+
34+
## Prerequisites
35+
36+
The scenario outlined in this tutorial assumes that you already have the following prerequisites:
37+
38+
* [An Azure AD tenant](https://docs.microsoft.com/azure/active-directory/develop/quickstart-create-new-tenant)
39+
* A user account in Azure AD with [permission](https://docs.microsoft.com/azure/active-directory/users-groups-roles/directory-assign-admin-roles) to configure provisioning (for example, Application Administrator, Cloud Application administrator, Application Owner, or Global Administrator).
40+
* A CheckProof account with **SCIM Provisioning** function enabled.
41+
42+
## Step 1. Plan your provisioning deployment
43+
1. Learn about [how the provisioning service works](https://docs.microsoft.com/azure/active-directory/manage-apps/user-provisioning).
44+
2. Determine who will be in [scope for provisioning](https://docs.microsoft.com/azure/active-directory/manage-apps/define-conditional-rules-for-provisioning-user-accounts).
45+
3. Determine what data to [map between Azure AD and CheckProof](https://docs.microsoft.com/azure/active-directory/manage-apps/customize-application-attributes).
46+
47+
## Step 2. Configure CheckProof to support provisioning with Azure AD
48+
49+
1. Log in to [CheckProof admin account](https://admin.checkproof.com/login).
50+
51+
2. Navigate to **Settings** > **Company Settings**.
52+
53+
![provision](media/checkproof-provisioning-tutorial/settings.png)
54+
55+
3. Click on the **PROVISIONING** tab.
56+
57+
4. The **Provisioning URL** and **Provisioning Secret Token** will be displayed. These values will be entered in the **Tenant URL** and **Secret Token** field in the Provisioning tab of your CheckProof application in the Azure portal.
58+
59+
![tenant](media/checkproof-provisioning-tutorial/token.png)
60+
61+
## Step 3. Add CheckProof from the Azure AD application gallery
62+
63+
Add CheckProof from the Azure AD application gallery to start managing provisioning to CheckProof. If you have previously setup CheckProof for SSO, you can use the same application. However it is recommended that you create a separate app when testing out the integration initially. Learn more about adding an application from the gallery [here](https://docs.microsoft.com/azure/active-directory/manage-apps/add-gallery-app).
64+
65+
## Step 4. Define who will be in scope for provisioning
66+
67+
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](https://docs.microsoft.com/azure/active-directory/manage-apps/define-conditional-rules-for-provisioning-user-accounts).
68+
69+
* When assigning users and groups to CheckProof, 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](https://docs.microsoft.com/azure/active-directory/develop/howto-add-app-roles-in-azure-ad-apps) to add additional roles.
70+
71+
* 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](https://docs.microsoft.com/azure/active-directory/manage-apps/define-conditional-rules-for-provisioning-user-accounts).
72+
73+
74+
## Step 5. Configure automatic user provisioning to CheckProof
75+
76+
This section guides you through the steps to configure the Azure AD provisioning service to create, update, and disable users and/or groups in CheckProof based on user and/or group assignments in Azure AD.
77+
78+
### To configure automatic user provisioning for CheckProof in Azure AD:
79+
80+
1. Sign in to the [Azure portal](https://portal.azure.com). Select **Enterprise Applications**, then select **All applications**.
81+
82+
![Enterprise applications blade](common/enterprise-applications.png)
83+
84+
2. In the applications list, select **CheckProof**.
85+
86+
![The CheckProof link in the Applications list](common/all-applications.png)
87+
88+
3. Select the **Provisioning** tab.
89+
90+
![Provisioning tab](common/provisioning.png)
91+
92+
4. Set the **Provisioning Mode** to **Automatic**.
93+
94+
![Provisioning tab automatic](common/provisioning-automatic.png)
95+
96+
5. Under the **Admin Credentials** section, input your CheckProof Tenant URL and Secret Token. Click **Test Connection** to ensure Azure AD can connect to CheckProof. If the connection fails, ensure your CheckProof account has Admin permissions and try again.
97+
98+
![Token](common/provisioning-testconnection-tenanturltoken.png)
99+
100+
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.
101+
102+
![Notification Email](common/provisioning-notification-email.png)
103+
104+
7. Select **Save**.
105+
106+
8. Under the **Mappings** section, select **Synchronize Azure Active Directory Users to CheckProof**.
107+
108+
9. Review the user attributes that are synchronized from Azure AD to CheckProof in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the user accounts in CheckProof for update operations. If you choose to change the [matching target attribute](https://docs.microsoft.com/azure/active-directory/manage-apps/customize-application-attributes), you will need to ensure that the CheckProof API supports filtering users based on that attribute. Select the **Save** button to commit any changes.
109+
110+
|Attribute|Type|Supported For Filtering|
111+
|---|---|--|
112+
|userName|String|✓|
113+
|active|Boolean|
114+
|roles|String|
115+
|displayName|String|
116+
|emails[type eq "work"].value|String|
117+
|preferredLanguage|String|
118+
|name.givenName|String|
119+
|name.familyName|String|
120+
|phoneNumbers[type eq "mobile"].value|String|
121+
|externalId|String|
122+
123+
10. Under the **Mappings** section, select **Synchronize Azure Active Directory Groups to CheckProof**.
124+
125+
11. Review the group attributes that are synchronized from Azure AD to CheckProof in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the groups in CheckProof for update operations. Select the **Save** button to commit any changes.
126+
127+
|Attribute|Type|Supported For Filtering|
128+
|---|---|--|
129+
|displayName|String|✓|
130+
|externalId|String|
131+
|members|Reference|
132+
133+
12. To configure scoping filters, refer to the following instructions provided in the [Scoping filter tutorial](../manage-apps/define-conditional-rules-for-provisioning-user-accounts.md).
134+
135+
13. To enable the Azure AD provisioning service for CheckProof, change the **Provisioning Status** to **On** in the **Settings** section.
136+
137+
![Provisioning Status Toggled On](common/provisioning-toggle-on.png)
138+
139+
14. Define the users and/or groups that you would like to provision to CheckProof by choosing the desired values in **Scope** in the **Settings** section.
140+
141+
![Provisioning Scope](common/provisioning-scope.png)
142+
143+
15. When you are ready to provision, click **Save**.
144+
145+
![Saving Provisioning Configuration](common/provisioning-configuration-save.png)
146+
147+
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 perform than subsequent cycles, which occur approximately every 40 minutes as long as the Azure AD provisioning service is running.
148+
149+
## Step 6. Monitor your deployment
150+
Once you've configured provisioning, use the following resources to monitor your deployment:
151+
152+
1. Use the [provisioning logs](https://docs.microsoft.com/azure/active-directory/reports-monitoring/concept-provisioning-logs) to determine which users have been provisioned successfully or unsuccessfully
153+
2. Check the [progress bar](https://docs.microsoft.com/azure/active-directory/app-provisioning/application-provisioning-when-will-provisioning-finish-specific-user) to see the status of the provisioning cycle and how close it is to completion
154+
3. If the provisioning configuration seems to be in an unhealthy state, the application will go into quarantine. Learn more about quarantine states [here](https://docs.microsoft.com/azure/active-directory/manage-apps/application-provisioning-quarantine-status).
155+
156+
## Additional resources
157+
158+
* [Managing user account provisioning for Enterprise Apps](../manage-apps/configure-automatic-user-provisioning-portal.md)
159+
* [What is application access and single sign-on with Azure Active Directory?](../manage-apps/what-is-single-sign-on.md)
160+
161+
## Next steps
162+
163+
* [Learn how to review logs and get reports on provisioning activity](../manage-apps/check-status-user-account-provisioning.md)

0 commit comments

Comments
 (0)