Skip to content

Commit 19dfdfa

Browse files
authored
Merge pull request #157851 from MicrosoftDocs/master
Merge master to live, 4 AM
2 parents 3de22db + ee46091 commit 19dfdfa

File tree

49 files changed

+1415
-191
lines changed

Some content is hidden

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

49 files changed

+1415
-191
lines changed

.openpublishing.redirection.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -47385,6 +47385,11 @@
4738547385
"redirect_url": "http://docs.microsoft.com/azure/cognitive-services/cognitive-services-support-options?context=/azure/cognitive-services/speech-service/context/context",
4738647386
"redirect_document_id": true
4738747387
},
47388+
{
47389+
"source_path_from_root": "/articles/cognitive-services/Speech-Service/speech-studio-test-model.md",
47390+
"redirect_url": "http://docs.microsoft.com/azure/cognitive-services/speech-service/speech-studio-overview",
47391+
"redirect_document_id": true
47392+
},
4738847393
{
4738947394
"source_path_from_root": "/articles/cognitive-services/Speech-Service/whats-new.md",
4739047395
"redirect_url": "http://docs.microsoft.com/azure/cognitive-services/speech-service/overview",

articles/active-directory-b2c/contentdefinitions.md

Lines changed: 46 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ manager: celestedg
99
ms.service: active-directory
1010
ms.workload: identity
1111
ms.topic: reference
12-
ms.date: 02/15/2021
12+
ms.date: 05/10/2021
1313
ms.author: mimart
1414
ms.subservice: B2C
1515
---
@@ -71,6 +71,26 @@ The **ContentDefinition** element contains the following elements:
7171
| Metadata | 0:1 | A collection of key/value pairs that contains the metadata utilized by the content definition. |
7272
| LocalizedResourcesReferences | 0:1 | A collection of localized resources references. Use this element to customize the localization of a user interface and claims attribute. |
7373

74+
### LoadUri
75+
76+
The **LoadUri** element is used to specify the URL of the HTML5 page for the content definition. The Azure AD B2C [custom policy starter-packs](https://github.com/Azure-Samples/active-directory-b2c-custom-policy-starterpack) come with content definitions that use Azure AD B2C HTML pages. The **LoadUri** starts with `~`, which is a relative path to your Azure AD B2C tenant.
77+
78+
```XML
79+
<ContentDefinition Id="api.signuporsignin">
80+
<LoadUri>~/tenant/templates/AzureBlue/unified.cshtml</LoadUri>
81+
...
82+
</ContentDefinition>
83+
```
84+
85+
You can [customize the user interface with HTML templates](customize-ui-with-html.md). When using HTML templates, provide an absolute URL. The following example illustrates a content definition with HTML template:
86+
87+
```XML
88+
<ContentDefinition Id="api.signuporsignin">
89+
<LoadUri>https://your-storage-account.blob.core.windows.net/your-container/customize-ui.html</LoadUri>
90+
...
91+
</ContentDefinition>
92+
```
93+
7494
### DataUri
7595

7696
The **DataUri** element is used to specify the page identifier. Azure AD B2C uses the page identifier to load and initiate UI elements and client side JavaScript. The format of the value is `urn:com:microsoft:aad:b2c:elements:page-name:version`. The following table lists the page identifiers you can use.
@@ -95,30 +115,36 @@ The [version](page-layout.md) part of the `DataUri` specifies the package of con
95115
The following example shows the **DataUri** of `selfasserted` version `1.2.0`:
96116

97117
```xml
98-
<ContentDefinition Id="api.localaccountpasswordreset">
99-
<LoadUri>~/tenant/templates/AzureBlue/selfAsserted.cshtml</LoadUri>
100-
<RecoveryUri>~/common/default_page_error.html</RecoveryUri>
101-
<DataUri>urn:com:microsoft:aad:b2c:elements:contract:selfasserted:1.2.0</DataUri>
102-
<Metadata>
103-
<Item Key="DisplayName">Local account change password page</Item>
104-
</Metadata>
105-
</ContentDefinition>
118+
<!--
119+
<BuildingBlocks>
120+
<ContentDefinitions>-->
121+
<ContentDefinition Id="api.localaccountpasswordreset">
122+
<LoadUri>~/tenant/templates/AzureBlue/selfAsserted.cshtml</LoadUri>
123+
<RecoveryUri>~/common/default_page_error.html</RecoveryUri>
124+
<DataUri>urn:com:microsoft:aad:b2c:elements:contract:selfasserted:1.2.0</DataUri>
125+
<Metadata>
126+
<Item Key="DisplayName">Local account change password page</Item>
127+
</Metadata>
128+
</ContentDefinition>
129+
<!--
130+
</ContentDefinitions>
131+
</BuildingBlocks> -->
106132
```
107133

108134
#### Migrating to page layout
109135

110-
The format of the value must contain the word `contract`: _urn:com:microsoft:aad:b2c:elements:**contract**:page-name:version_. To specify a page layout in your custom policies that use an old **DataUri** value, use following table to migrate to the new format.
136+
To migrate from the old **DataUri** value (without page contract) to page layout version, add the word `contract` follow by a page version. Use following table to migrate from the old **DataUri** value to page layout version.
111137

112138
| Old DataUri value | New DataUri value |
113139
| ----------------- | ----------------- |
114140
| `urn:com:microsoft:aad:b2c:elements:globalexception:1.0.0` | `urn:com:microsoft:aad:b2c:elements:contract:globalexception:1.2.1` |
115141
| `urn:com:microsoft:aad:b2c:elements:globalexception:1.1.0` | `urn:com:microsoft:aad:b2c:elements:contract:globalexception:1.2.1` |
116142
| `urn:com:microsoft:aad:b2c:elements:idpselection:1.0.0` | `urn:com:microsoft:aad:b2c:elements:contract:providerselection:1.2.1` |
117-
| `urn:com:microsoft:aad:b2c:elements:selfasserted:1.0.0` | `urn:com:microsoft:aad:b2c:elements:contract:selfasserted:2.1.2` |
118-
| `urn:com:microsoft:aad:b2c:elements:selfasserted:1.1.0` | `urn:com:microsoft:aad:b2c:elements:contract:selfasserted:2.1.2` |
119-
| `urn:com:microsoft:aad:b2c:elements:unifiedssd:1.0.0` | `urn:com:microsoft:aad:b2c:elements:contract:unifiedssd:2.1.2` |
120-
| `urn:com:microsoft:aad:b2c:elements:unifiedssp:1.0.0` | `urn:com:microsoft:aad:b2c:elements:contract:unifiedssp:2.1.2` |
121-
| `urn:com:microsoft:aad:b2c:elements:unifiedssp:1.1.0` | `urn:com:microsoft:aad:b2c:elements:contract:unifiedssp:2.1.2` |
143+
| `urn:com:microsoft:aad:b2c:elements:selfasserted:1.0.0` | `urn:com:microsoft:aad:b2c:elements:contract:selfasserted:2.1.4` |
144+
| `urn:com:microsoft:aad:b2c:elements:selfasserted:1.1.0` | `urn:com:microsoft:aad:b2c:elements:contract:selfasserted:2.1.4` |
145+
| `urn:com:microsoft:aad:b2c:elements:unifiedssd:1.0.0` | `urn:com:microsoft:aad:b2c:elements:contract:unifiedssd:2.1.4` |
146+
| `urn:com:microsoft:aad:b2c:elements:unifiedssp:1.0.0` | `urn:com:microsoft:aad:b2c:elements:contract:unifiedssp:2.1.4` |
147+
| `urn:com:microsoft:aad:b2c:elements:unifiedssp:1.1.0` | `urn:com:microsoft:aad:b2c:elements:contract:unifiedssp:2.1.4` |
122148
| `urn:com:microsoft:aad:b2c:elements:multifactor:1.0.0` | `urn:com:microsoft:aad:b2c:elements:contract:multifactor:1.2.0` |
123149
| `urn:com:microsoft:aad:b2c:elements:multifactor:1.1.0` | `urn:com:microsoft:aad:b2c:elements:contract:multifactor:1.2.0` |
124150

@@ -138,19 +164,19 @@ The following example shows the content definition identifiers and the correspon
138164
<DataUri>urn:com:microsoft:aad:b2c:elements:contract:providerselection:1.2.1</DataUri>
139165
</ContentDefinition>
140166
<ContentDefinition Id="api.signuporsignin">
141-
<DataUri>urn:com:microsoft:aad:b2c:elements:contract:unifiedssp:2.1.2</DataUri>
167+
<DataUri>urn:com:microsoft:aad:b2c:elements:contract:unifiedssp:2.1.4</DataUri>
142168
</ContentDefinition>
143169
<ContentDefinition Id="api.selfasserted">
144-
<DataUri>urn:com:microsoft:aad:b2c:elements:contract:selfasserted:2.1.2</DataUri>
170+
<DataUri>urn:com:microsoft:aad:b2c:elements:contract:selfasserted:2.1.4</DataUri>
145171
</ContentDefinition>
146172
<ContentDefinition Id="api.selfasserted.profileupdate">
147-
<DataUri>urn:com:microsoft:aad:b2c:elements:contract:selfasserted:2.1.2</DataUri>
173+
<DataUri>urn:com:microsoft:aad:b2c:elements:contract:selfasserted:2.1.4</DataUri>
148174
</ContentDefinition>
149175
<ContentDefinition Id="api.localaccountsignup">
150-
<DataUri>urn:com:microsoft:aad:b2c:elements:contract:selfasserted:2.1.2</DataUri>
176+
<DataUri>urn:com:microsoft:aad:b2c:elements:contract:selfasserted:2.1.4</DataUri>
151177
</ContentDefinition>
152178
<ContentDefinition Id="api.localaccountpasswordreset">
153-
<DataUri>urn:com:microsoft:aad:b2c:elements:contract:selfasserted:2.1.2</DataUri>
179+
<DataUri>urn:com:microsoft:aad:b2c:elements:contract:selfasserted:2.1.4</DataUri>
154180
</ContentDefinition>
155181
<ContentDefinition Id="api.phonefactor">
156182
<DataUri>urn:com:microsoft:aad:b2c:elements:contract:multifactor:1.2.2</DataUri>

articles/active-directory-b2c/technicalprofiles.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ manager: celestedg
99
ms.service: active-directory
1010
ms.workload: identity
1111
ms.topic: reference
12-
ms.date: 03/04/2021
12+
ms.date: 05/10/2021
1313
ms.author: mimart
1414
ms.subservice: B2C
1515
---
@@ -479,10 +479,10 @@ The following example illustrates the use of the inclusion:
479479
</TechnicalProfile>
480480

481481
<TechnicalProfile Id="REST-UpdateProfile">
482-
<Metadata>
482+
<DisplayName>Update the user profile</DisplayName>
483+
<Metadata>
483484
<Item Key="ServiceUrl">https://your-app-name.azurewebsites.NET/api/identity/update</Item>
484485
</Metadata>
485-
<DisplayName>Update the user profile</DisplayName>
486486
<InputClaims>
487487
<InputClaim ClaimTypeReferenceId="objectId" />
488488
<InputClaim ClaimTypeReferenceId="email" />
Lines changed: 178 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,178 @@
1+
---
2+
title: 'Tutorial: Azure Active Directory single sign-on (SSO) integration with Ardoq | Microsoft Docs'
3+
description: Learn how to configure single sign-on between Azure Active Directory and Ardoq.
4+
services: active-directory
5+
author: jeevansd
6+
manager: CelesteDG
7+
ms.reviewer: CelesteDG
8+
ms.service: active-directory
9+
ms.subservice: saas-app-tutorial
10+
ms.workload: identity
11+
ms.topic: tutorial
12+
ms.date: 05/07/2021
13+
ms.author: jeedes
14+
15+
---
16+
17+
# Tutorial: Azure Active Directory single sign-on (SSO) integration with Ardoq
18+
19+
In this tutorial, you'll learn how to integrate Ardoq with Azure Active Directory (Azure AD). When you integrate Ardoq with Azure AD, you can:
20+
21+
* Control in Azure AD who has access to Ardoq.
22+
* Enable your users to be automatically signed-in to Ardoq with their Azure AD accounts.
23+
* Manage your accounts in one central location - the Azure portal.
24+
25+
## Prerequisites
26+
27+
To get started, you need the following items:
28+
29+
* An Azure AD subscription. If you don't have a subscription, you can get a [free account](https://azure.microsoft.com/free/).
30+
* Ardoq single sign-on (SSO) enabled subscription.
31+
32+
## Scenario description
33+
34+
In this tutorial, you configure and test Azure AD SSO in a test environment.
35+
36+
* Ardoq supports **SP and IDP** initiated SSO.
37+
* Ardoq supports **Just In Time** user provisioning.
38+
39+
## Adding Ardoq from the gallery
40+
41+
To configure the integration of Ardoq into Azure AD, you need to add Ardoq from the gallery to your list of managed SaaS apps.
42+
43+
1. Sign in to the Azure portal using either a work or school account, or a personal Microsoft account.
44+
1. On the left navigation pane, select the **Azure Active Directory** service.
45+
1. Navigate to **Enterprise Applications** and then select **All Applications**.
46+
1. To add new application, select **New application**.
47+
1. In the **Add from the gallery** section, type **Ardoq** in the search box.
48+
1. Select **Ardoq** from results panel and then add the app. Wait a few seconds while the app is added to your tenant.
49+
50+
51+
## Configure and test Azure AD SSO for Ardoq
52+
53+
Configure and test Azure AD SSO with Ardoq using a test user called **B.Simon**. For SSO to work, you need to establish a link relationship between an Azure AD user and the related user in Ardoq.
54+
55+
To configure and test Azure AD SSO with Ardoq, perform the following steps:
56+
57+
1. **[Configure Azure AD SSO](#configure-azure-ad-sso)** - to enable your users to use this feature.
58+
1. **[Create an Azure AD test user](#create-an-azure-ad-test-user)** - to test Azure AD single sign-on with B.Simon.
59+
1. **[Assign the Azure AD test user](#assign-the-azure-ad-test-user)** - to enable B.Simon to use Azure AD single sign-on.
60+
1. **[Configure Ardoq SSO](#configure-ardoq-sso)** - to configure the single sign-on settings on application side.
61+
1. **[Create Ardoq test user](#create-ardoq-test-user)** - to have a counterpart of B.Simon in Ardoq that is linked to the Azure AD representation of user.
62+
1. **[Test SSO](#test-sso)** - to verify whether the configuration works.
63+
64+
## Configure Azure AD SSO
65+
66+
Follow these steps to enable Azure AD SSO in the Azure portal.
67+
68+
1. In the Azure portal, on the **Ardoq** application integration page, find the **Manage** section and select **single sign-on**.
69+
1. On the **Select a single sign-on method** page, select **SAML**.
70+
1. On the **Set up single sign-on with SAML** page, click the pencil icon for **Basic SAML Configuration** to edit the settings.
71+
72+
![Edit Basic SAML Configuration](common/edit-urls.png)
73+
74+
1. On the **Basic SAML Configuration** section, if you wish to configure the application in **IDP** initiated mode, enter the values for the following fields:
75+
76+
a. In the **Identifier** text box, type a URL using one of the following patterns:
77+
78+
| Identifier |
79+
|------------|
80+
| `https://<CustomerName>.us.ardoq.com/saml/v2` |
81+
| `https://<CustomerName>.ardoq.com/saml/v2` |
82+
|
83+
84+
85+
b. In the **Reply URL** text box, type a URL using the following pattern:
86+
`https://<CustomerName>.ardoq.com/saml/v2`
87+
88+
1. Click **Set additional URLs** and perform the following step if you wish to configure the application in **SP** initiated mode:
89+
90+
In the **Sign-on URL** text box, type a URL using one of the following patterns:
91+
92+
| Sign-on URL |
93+
|-------------|
94+
| `https://<CustomerName>.ardoq.com/saml/v2` |
95+
| `https://<CustomerName>.us.ardoq.com/saml/v2` |
96+
|
97+
98+
> [!NOTE]
99+
> These values are not real. Update these values with the actual Identifier, Reply URL and Sign-on URL. Contact [Ardoq Client support team](mailto:[email protected]) to get these values. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
100+
101+
1. Ardoq application expects the SAML assertions in a specific format, which requires you to add custom attribute mappings to your SAML token attributes configuration. The following screenshot shows the list of default attributes.
102+
103+
![image](common/default-attributes.png)
104+
105+
1. In addition to above, Ardoq application expects few more attributes to be passed back in SAML response which are shown below. These attributes are also pre populated but you can review them as per your requirements.
106+
107+
| Name | Source Attribute|
108+
| -------------- | --------- |
109+
| displayName | user.displayname |
110+
| assignedRoles | user.assignedroles |
111+
| mail | user.mail |
112+
113+
> [!NOTE]
114+
> Ardoq expects roles for users assigned to the application. Please set up these roles in Azure AD so that users can be assigned the appropriate roles. To understand how to configure roles in Azure AD, see [here](https://docs.microsoft.com/azure/active-directory/develop/howto-add-app-roles-in-azure-ad-apps#app-roles-ui).
115+
116+
117+
1. On the **Set up single sign-on with SAML** page, in the **SAML Signing Certificate** section, find **Federation Metadata XML** and select **Download** to download the certificate and save it on your computer.
118+
119+
![The Certificate download link](common/metadataxml.png)
120+
121+
1. On the **Set up Ardoq** section, copy the appropriate URL(s) based on your requirement.
122+
123+
![Copy configuration URLs](common/copy-configuration-urls.png)
124+
125+
### Create an Azure AD test user
126+
127+
In this section, you'll create a test user in the Azure portal called B.Simon.
128+
129+
1. From the left pane in the Azure portal, select **Azure Active Directory**, select **Users**, and then select **All users**.
130+
1. Select **New user** at the top of the screen.
131+
1. In the **User** properties, follow these steps:
132+
1. In the **Name** field, enter `B.Simon`.
133+
1. In the **User name** field, enter the [email protected]. For example, `[email protected]`.
134+
1. Select the **Show password** check box, and then write down the value that's displayed in the **Password** box.
135+
1. Click **Create**.
136+
137+
### Assign the Azure AD test user
138+
139+
In this section, you'll enable B.Simon to use Azure single sign-on by granting access to Ardoq.
140+
141+
1. In the Azure portal, select **Enterprise Applications**, and then select **All applications**.
142+
1. In the applications list, select **Ardoq**.
143+
1. In the app's overview page, find the **Manage** section and select **Users and groups**.
144+
1. Select **Add user**, then select **Users and groups** in the **Add Assignment** dialog.
145+
1. In the **Users and groups** dialog, select **B.Simon** from the Users list, then click the **Select** button at the bottom of the screen.
146+
1. If you have setup the roles as explained in the above, you can select it from the **Select a role** dropdown.
147+
1. In the **Add Assignment** dialog, click the **Assign** button.
148+
149+
## Configure Ardoq SSO
150+
151+
To configure single sign-on on **Ardoq** side, you need to send the downloaded **Federation Metadata XML** and appropriate copied URLs from Azure portal to [Ardoq support team](mailto:[email protected]). They set this setting to have the SAML SSO connection set properly on both sides.
152+
153+
### Create Ardoq test user
154+
155+
In this section, a user called Britta Simon is created in Ardoq. Ardoq supports just-in-time user provisioning, which is enabled by default. There is no action item for you in this section. If a user doesn't already exist in Ardoq, a new one is created after authentication.
156+
157+
## Test SSO
158+
159+
In this section, you test your Azure AD single sign-on configuration with following options.
160+
161+
#### SP initiated:
162+
163+
* Click on **Test this application** in Azure portal. This will redirect to Ardoq Sign on URL where you can initiate the login flow.
164+
165+
* Go to Ardoq Sign-on URL directly and initiate the login flow from there.
166+
167+
#### IDP initiated:
168+
169+
* Click on **Test this application** in Azure portal and you should be automatically signed in to the Ardoq for which you set up the SSO
170+
171+
You can also use Microsoft My Apps to test the application in any mode. When you click the Ardoq tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Ardoq for which you set up the SSO. For more information about the My Apps, see [Introduction to the My Apps](https://docs.microsoft.com/azure/active-directory/active-directory-saas-access-panel-introduction).
172+
173+
174+
## Next steps
175+
176+
Once you configure Ardoq you can enforce session control, which protects exfiltration and infiltration of your organization’s sensitive data in real time. Session control extends from Conditional Access. [Learn how to enforce session control with Microsoft Cloud App Security](https://docs.microsoft.com/cloud-app-security/proxy-deployment-any-app).
177+
178+

0 commit comments

Comments
 (0)