Skip to content

Commit ab6f059

Browse files
authored
Merge pull request #229540 from v-missam/netsparker
create doc
2 parents 708b16b + f16694d commit ab6f059

File tree

4 files changed

+445
-1
lines changed

4 files changed

+445
-1
lines changed
Lines changed: 152 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,152 @@
1+
---
2+
title: 'Tutorial: Configure Acunetix 360 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 Acunetix 360.
4+
services: active-directory
5+
author: twimmers
6+
writer: twimmers
7+
manager: beatrizd
8+
ms.assetid: cb0c2e2c-ade9-4e6b-9ce5-d7c7d2743d90
9+
ms.service: active-directory
10+
ms.subservice: saas-app-tutorial
11+
ms.workload: identity
12+
ms.topic: tutorial
13+
ms.date: 03/06/2023
14+
ms.author: thwimmer
15+
---
16+
17+
# Tutorial: Configure Acunetix 360 for automatic user provisioning
18+
19+
This tutorial describes the steps you need to perform in both Acunetix 360 and Azure Active Directory (Azure AD) to configure automatic user provisioning. When configured, Azure AD automatically provisions and de-provisions users and groups to [Acunetix 360](https://www.acunetix.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).
20+
21+
22+
## Supported capabilities
23+
> [!div class="checklist"]
24+
> * Create users in Acunetix 360.
25+
> * Remove users in Acunetix 360 when they do not require access anymore.
26+
> * Keep user attributes synchronized between Azure AD and Acunetix 360.
27+
> * Provision groups and group memberships in Acunetix 360
28+
> * [Single sign-on](acunetix-360-tutorial.md) to Acunetix 360 (recommended).
29+
30+
## Prerequisites
31+
32+
The scenario outlined in this tutorial assumes that you already have the following prerequisites:
33+
34+
* [An Azure AD tenant](../develop/quickstart-create-new-tenant.md)
35+
* 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).
36+
* An administrator account with Acunetix 360.
37+
38+
## Step 1. Plan your provisioning deployment
39+
1. Learn about [how the provisioning service works](../app-provisioning/user-provisioning.md).
40+
1. Determine who will be in [scope for provisioning](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
41+
1. Determine what data to [map between Azure AD and Acunetix 360](../app-provisioning/customize-application-attributes.md).
42+
43+
## Step 2. Configure Acunetix 360 to support provisioning with Azure AD
44+
45+
1. Log in to [Acunetix 360 admin console](https://online.acunetix360.com/).
46+
1. Click on profile logo and navigate to **API Settings**.
47+
1. Enter your **Current Password** and then click on **Submit**.
48+
1. Copy and save the **Token**.This value will be entered in the **Secret Token** field in the Provisioning tab of your Acunetix 360 application in the Azure portal.
49+
>[!NOTE]
50+
>Click on **Reset API Token** in order to reset the Token.
51+
1. And `https://online.acunetix360.com/scim/v2` will be entered in the **Tenant Url** field in the Provisioning tab of your Acunetix 360 application in the Azure portal.
52+
53+
54+
55+
## Step 3. Add Acunetix 360 from the Azure AD application gallery
56+
57+
Add Acunetix 360 from the Azure AD application gallery to start managing provisioning to Acunetix 360. If you have previously setup Acunetix 360 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).
58+
59+
## Step 4. Define who will be in scope for provisioning
60+
61+
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).
62+
63+
* 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).
64+
65+
* If you need more roles, you can [update the application manifest](../develop/howto-add-app-roles-in-azure-ad-apps.md) to add new roles.
66+
67+
68+
## Step 5. Configure automatic user provisioning to Acunetix 360
69+
70+
This section guides you through the steps to configure the Azure AD provisioning service to create, update, and disable users and/or groups in TestApp based on user and/or group assignments in Azure AD.
71+
72+
### To configure automatic user provisioning for Acunetix 360 in Azure AD:
73+
74+
1. Sign in to the [Azure portal](https://portal.azure.com). Select **Enterprise Applications**, then select **All applications**.
75+
76+
![Screenshot of Enterprise applications blade.](common/enterprise-applications.png)
77+
78+
1. In the applications list, select **Acunetix 360**.
79+
80+
![Screenshot of the Acunetix 360 link in the Applications list.](common/all-applications.png)
81+
82+
1. Select the **Provisioning** tab.
83+
84+
![Screenshot of Provisioning tab.](common/provisioning.png)
85+
86+
1. Set the **Provisioning Mode** to **Automatic**.
87+
88+
![Screenshot of Provisioning tab automatic.](common/provisioning-automatic.png)
89+
90+
1. Under the **Admin Credentials** section, input your Acunetix 360 Tenant URL and Secret Token. Click **Test Connection** to ensure Azure AD can connect to Acunetix 360. If the connection fails, ensure your Acunetix 360 account has Admin permissions and try again.
91+
92+
![Screenshot of Token.](common/provisioning-testconnection-tenanturltoken.png)
93+
94+
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.
95+
96+
![Screenshot of Notification Email.](common/provisioning-notification-email.png)
97+
98+
1. Select **Save**.
99+
100+
1. Under the **Mappings** section, select **Synchronize Azure Active Directory Users to Acunetix 360**.
101+
102+
1. Review the user attributes that are synchronized from Azure AD to Acunetix 360 in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the user accounts in Acunetix 360 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 Acunetix 360 API supports filtering users based on that attribute. Select the **Save** button to commit any changes.
103+
104+
|Attribute|Type|Supported for filtering|Required by Acunetix 360|
105+
|---|---|---|---|
106+
|userName|String|✓|✓
107+
|active|Boolean||✓
108+
|emails[type eq "work"].value|String||✓
109+
|name.givenName|String||✓
110+
|name.familyName|String||✓
111+
|phoneNumbers[type eq "mobile"].value|String||
112+
113+
1. Under the **Mappings** section, select **Synchronize Azure Active Directory Groups to Acunetix 360**.
114+
115+
1. Review the group attributes that are synchronized from Azure AD to Acunetix 360 in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the groups in Acunetix 360 for update operations. Select the **Save** button to commit any changes.
116+
117+
|Attribute|Type|Supported for filtering|Required by Acunetix 360|
118+
|---|---|---|---|
119+
|displayName|String|✓|✓
120+
|members|Reference||
121+
122+
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).
123+
124+
1. To enable the Azure AD provisioning service for Acunetix 360, change the **Provisioning Status** to **On** in the **Settings** section.
125+
126+
![Screenshot of Provisioning Status Toggled On.](common/provisioning-toggle-on.png)
127+
128+
1. Define the users and/or groups that you would like to provision to Acunetix 360 by choosing the desired values in **Scope** in the **Settings** section.
129+
130+
![Screenshot of Provisioning Scope.](common/provisioning-scope.png)
131+
132+
1. When you're ready to provision, click **Save**.
133+
134+
![Screenshot of Saving Provisioning Configuration.](common/provisioning-configuration-save.png)
135+
136+
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.
137+
138+
## Step 6. Monitor your deployment
139+
Once you've configured provisioning, use the following resources to monitor your deployment:
140+
141+
* Use the [provisioning logs](../reports-monitoring/concept-provisioning-logs.md) to determine which users have been provisioned successfully or unsuccessfully
142+
* 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
143+
* If the provisioning configuration seems to be in an unhealthy state, the application goes into quarantine. Learn more about quarantine states [here](../app-provisioning/application-provisioning-quarantine-status.md).
144+
145+
## More resources
146+
147+
* [Managing user account provisioning for Enterprise Apps](../app-provisioning/configure-automatic-user-provisioning-portal.md)
148+
* [What is application access and single sign-on with Azure Active Directory?](../manage-apps/what-is-single-sign-on.md)
149+
150+
## Next steps
151+
152+
* [Learn how to review logs and get reports on provisioning activity](../app-provisioning/check-status-user-account-provisioning.md)
Lines changed: 136 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,136 @@
1+
---
2+
title: 'Tutorial: Configure Ardoq 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 Ardoq.
4+
services: active-directory
5+
author: twimmers
6+
writer: twimmers
7+
manager: beatrizd
8+
ms.assetid: 0339e63a-5262-4019-a85d-18c9617fc4b3
9+
ms.service: active-directory
10+
ms.subservice: saas-app-tutorial
11+
ms.workload: identity
12+
ms.topic: tutorial
13+
ms.date: 03/02/2023
14+
ms.author: thwimmer
15+
---
16+
17+
# Tutorial: Configure Ardoq for automatic user provisioning
18+
19+
This tutorial describes the steps you need to perform in both Ardoq and Azure Active Directory (Azure AD) to configure automatic user provisioning. When configured, Azure AD automatically provisions and de-provisions users to [Ardoq](https://www.ardoq.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).
20+
21+
22+
## Supported capabilities
23+
> [!div class="checklist"]
24+
> * Create users in Ardoq.
25+
> * Remove users in Ardoq when they do not require access anymore.
26+
> * Keep user attributes synchronized between Azure AD and Ardoq.
27+
> * [Single sign-on](ardoq-tutorial.md) to Ardoq (recommended).
28+
29+
## Prerequisites
30+
31+
The scenario outlined in this tutorial assumes that you already have the following prerequisites:
32+
33+
* [An Azure AD tenant](../develop/quickstart-create-new-tenant.md)
34+
* 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).
35+
* An administrator account with Ardoq.
36+
37+
## Step 1. Plan your provisioning deployment
38+
1. Learn about [how the provisioning service works](../app-provisioning/user-provisioning.md).
39+
1. Determine who will be in [scope for provisioning](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
40+
1. Determine what data to [map between Azure AD and Ardoq](../app-provisioning/customize-application-attributes.md).
41+
42+
## Step 2. Configure Ardoq to support provisioning with Azure AD
43+
44+
1. Log in to [Ardoq](https://aad.ardoq.com/).
45+
1. In the left menu click on profile logo and, navigate to **Organization Settings->Manage Organization->Manage SCIM Token**.
46+
1. Click on **Generate new**.
47+
1. Copy and save the **Token**.This value will be entered in the **Secret Token** field in the Provisioning tab of your Ardoq application in the Azure portal.
48+
1. And `https://aad.ardoq.com/api/scim/v2` will be entered in the **Tenant Url** field in the Provisioning tab of your Ardoq application in the Azure portal.
49+
50+
## Step 3. Add Ardoq from the Azure AD application gallery
51+
52+
Add Ardoq from the Azure AD application gallery to start managing provisioning to Ardoq. If you have previously setup Ardoq 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).
53+
54+
## Step 4. Define who will be in scope for provisioning
55+
56+
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. 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 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).
57+
58+
* Start small. Test with a small set of users before rolling out to everyone. When scope for provisioning is set to assigned users, you can control this by assigning one or two users to the app. When scope is set to all users, you can specify an [attribute based scoping filter](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
59+
60+
* If you need more roles, you can [update the application manifest](../develop/howto-add-app-roles-in-azure-ad-apps.md) to add new roles.
61+
62+
63+
## Step 5. Configure automatic user provisioning to Ardoq
64+
65+
This section guides you through the steps to configure the Azure AD provisioning service to create, update, and disable users in TestApp based on user and/or group assignments in Azure AD.
66+
67+
### To configure automatic user provisioning for Ardoq in Azure AD:
68+
69+
1. Sign in to the [Azure portal](https://portal.azure.com). Select **Enterprise Applications**, then select **All applications**.
70+
71+
![Screenshot of Enterprise applications blade.](common/enterprise-applications.png)
72+
73+
1. In the applications list, select **Ardoq**.
74+
75+
![Screenshot of the Ardoq link in the Applications list.](common/all-applications.png)
76+
77+
1. Select the **Provisioning** tab.
78+
79+
![Screenshot of Provisioning tab.](common/provisioning.png)
80+
81+
1. Set the **Provisioning Mode** to **Automatic**.
82+
83+
![Screenshot of Provisioning tab automatic.](common/provisioning-automatic.png)
84+
85+
1. Under the **Admin Credentials** section, input your Ardoq Tenant URL and Secret Token. Click **Test Connection** to ensure Azure AD can connect to Ardoq. If the connection fails, ensure your Ardoq account has Admin permissions and try again.
86+
87+
![Screenshot of Token.](common/provisioning-testconnection-tenanturltoken.png)
88+
89+
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.
90+
91+
![Screenshot of Notification Email.](common/provisioning-notification-email.png)
92+
93+
1. Select **Save**.
94+
95+
1. Under the **Mappings** section, select **Synchronize Azure Active Directory Users to Ardoq**.
96+
97+
1. Review the user attributes that are synchronized from Azure AD to Ardoq in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the user accounts in Ardoq 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 Ardoq API supports filtering users based on that attribute. Select the **Save** button to commit any changes.
98+
99+
|Attribute|Type|Supported for filtering|Required by Ardoq|
100+
|---|---|---|---|
101+
|userName|String|✓|✓
102+
|active|Boolean||✓
103+
|displayName|String||✓
104+
|roles[primary eq "True"].value|String||✓
105+
106+
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).
107+
108+
1. To enable the Azure AD provisioning service for Ardoq, change the **Provisioning Status** to **On** in the **Settings** section.
109+
110+
![Screenshot of Provisioning Status Toggled On.](common/provisioning-toggle-on.png)
111+
112+
1. Define the users that you would like to provision to Ardoq by choosing the desired values in **Scope** in the **Settings** section.
113+
114+
![Screenshot of Provisioning Scope.](common/provisioning-scope.png)
115+
116+
1. When you're ready to provision, click **Save**.
117+
118+
![Screenshot of Saving Provisioning Configuration.](common/provisioning-configuration-save.png)
119+
120+
This operation starts the initial synchronization cycle of all users 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.
121+
122+
## Step 6. Monitor your deployment
123+
Once you've configured provisioning, use the following resources to monitor your deployment:
124+
125+
* Use the [provisioning logs](../reports-monitoring/concept-provisioning-logs.md) to determine which users have been provisioned successfully or unsuccessfully
126+
* 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
127+
* If the provisioning configuration seems to be in an unhealthy state, the application goes into quarantine. Learn more about quarantine states [here](../app-provisioning/application-provisioning-quarantine-status.md).
128+
129+
## More resources
130+
131+
* [Managing user account provisioning for Enterprise Apps](../app-provisioning/configure-automatic-user-provisioning-portal.md)
132+
* [What is application access and single sign-on with Azure Active Directory?](../manage-apps/what-is-single-sign-on.md)
133+
134+
## Next steps
135+
136+
* [Learn how to review logs and get reports on provisioning activity](../app-provisioning/check-status-user-account-provisioning.md)

0 commit comments

Comments
 (0)