Skip to content

Commit dca0148

Browse files
Merge pull request #104611 from MicrosoftDocs/master
Merge master to live, 4 AM
2 parents ef568f5 + 1610d73 commit dca0148

File tree

43 files changed

+1237
-733
lines changed

Some content is hidden

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

43 files changed

+1237
-733
lines changed

articles/active-directory-b2c/claim-resolver-overview.md

Lines changed: 14 additions & 2 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/13/2020
12+
ms.date: 02/17/2020
1313
ms.author: marsma
1414
ms.subservice: B2C
1515
---
@@ -100,6 +100,18 @@ Any parameter name included as part of an OIDC or OAuth2 request can be mapped t
100100
| ----- | ----------------------- | --------|
101101
| {oauth2:access_token} | The access token. | N/A |
102102

103+
104+
### SAML
105+
106+
| Claim | Description | Example |
107+
| ----- | ----------- | --------|
108+
| {SAML:AuthnContextClassReferences} | The `AuthnContextClassRef` element value, from the SAML request. | urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport |
109+
| {SAML:NameIdPolicyFormat} | The `Format` attribute, from the `NameIDPolicy` element of the SAML request. | urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress |
110+
| {SAML:Issuer} | The SAML `Issuer` element value of the SAML request.| https://contoso.com |
111+
| {SAML:AllowCreate} | The `AllowCreate` attribute value, from the `NameIDPolicy` element of the SAML request. | True |
112+
| {SAML:ForceAuthn} | The `ForceAuthN` attribute value, from the `AuthnRequest` element of the SAML request. | True |
113+
| {SAML:ProviderName} | The `ProviderName` attribute value, from the `AuthnRequest` element of the SAML request.| Contoso.com |
114+
103115
## Using claim resolvers
104116

105117
You can use claims resolvers with the following elements:
@@ -228,4 +240,4 @@ In a [Relying party](relyingparty.md) policy technical profile, you may want to
228240
<SubjectNamingInfo ClaimType="sub" />
229241
</TechnicalProfile>
230242
</RelyingParty>
231-
```
243+
```

articles/active-directory-b2c/contentdefinitions.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: 02/16/2020
12+
ms.date: 02/17/2020
1313
ms.author: marsma
1414
ms.subservice: B2C
1515
---
@@ -66,7 +66,7 @@ The **ContentDefinition** element contains the following elements:
6666
| Element | Occurrences | Description |
6767
| ------- | ----------- | ----------- |
6868
| LoadUri | 1:1 | A string that contains the URL of the HTML5 page for the content definition. |
69-
| RecoveryUri | 0:1 | A string that contains the URL of the HTML page for displaying an error relating to the content definition. |
69+
| RecoveryUri | 1:1 | A string that contains the URL of the HTML page for displaying an error relating to the content definition. |
7070
| DataUri | 1:1 | A string that contains the relative URL of an HTML file that provides the user experience to invoke for the step. |
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. |
@@ -82,7 +82,7 @@ The **DataUri** element is used to specify the page identifier. Azure AD B2C use
8282
| `unifiedssp` | Displays a form for signing in with a local account that's based on an email address or a user name. This value also provides the “keep me sign-in functionality” and “Forgot your password?” link. |
8383
| `unifiedssd` | Displays a form for signing in with a local account that's based on an email address or a user name. |
8484
| `multifactor` | Verifies phone numbers by using text or voice during sign-up or sign-in. |
85-
| `selfasserted` | Displays a form that enables users to create or update their profile. |
85+
| `selfasserted` | Displays a form to collect data from a user. For example, enables users to create or update their profile. |
8686

8787
### Select a page layout
8888

articles/active-directory-b2c/self-asserted-technical-profile.md

Lines changed: 2 additions & 2 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/16/2020
12+
ms.date: 02/17/2020
1313
ms.author: marsma
1414
ms.subservice: B2C
1515
---
@@ -52,7 +52,7 @@ In a self-asserted technical profile, you can use the **InputClaims** and **Inpu
5252

5353
The display claims feature is currently in **preview**.
5454

55-
The **DisplayClaims** element contains a list of claims to be presented on the screen for collecting data from the user. To prepopulate the values of output claims, use the input claims that were previously described. The element may also contain a default value.
55+
The **DisplayClaims** element contains a list of claims to be presented on the screen for collecting data from the user. To prepopulate the values of display claims, use the input claims that were previously described. The element may also contain a default value.
5656

5757
The order of the claims in **DisplayClaims** specifies the order in which Azure AD B2C renders the claims on the screen. To force the user to provide a value for a specific claim, set the **Required** attribute of the **DisplayClaim** element to `true`.
5858

articles/active-directory-b2c/technicalprofiles.md

Lines changed: 2 additions & 2 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: 01/29/2020
12+
ms.date: 02/17/2020
1313
ms.author: marsma
1414
ms.subservice: B2C
1515
---
@@ -107,7 +107,7 @@ The **Protocol** element contains the following attributes:
107107

108108
| Attribute | Required | Description |
109109
| --------- | -------- | ----------- |
110-
| Name | Yes | The name of a valid protocol supported by Azure AD B2C that is used as part of the technical profile. Possible values: `OAuth1`, `OAuth2`, `SAML2`, `OpenIdConnect`, `Proprietary`, `session management`, `self-asserted`, or `None`. |
110+
| Name | Yes | The name of a valid protocol supported by Azure AD B2C that is used as part of the technical profile. Possible values: `OAuth1`, `OAuth2`, `SAML2`, `OpenIdConnect`, `Proprietary`, or `None`. |
111111
| Handler | No | When the protocol name is set to `Proprietary`, specify the fully-qualified name of the assembly that is used by Azure AD B2C to determine the protocol handler. |
112112

113113
## Metadata

articles/active-directory/managed-identities-azure-resources/services-support-managed-identities.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: List of services that support managed identities for Azure resource
44
services: active-directory
55
author: MarkusVi
66
ms.author: markvi
7-
ms.date: 09/24/2019
7+
ms.date: 02/13/2020
88
ms.topic: conceptual
99
ms.service: active-directory
1010
ms.subservice: msi
@@ -109,7 +109,7 @@ Refer to the following list to configure managed identity for Azure Logic Apps (
109109

110110
Managed identity type | All Generally Available<br>Global Azure Regions | Azure Government | Azure Germany | Azure China 21Vianet |
111111
| --- | --- | --- | --- | --- |
112-
| System assigned | Available | Not available | Not available | Not available |
112+
| System assigned | Available | Available | Not available | Available |
113113
| User assigned | Not available | Not available | Not available | Not available |
114114

115115
Refer to the following list to configure managed identity for Azure Data Factory V2 (in regions where available):
12.3 KB
Loading
8.22 KB
Loading
11.5 KB
Loading
17 KB
Loading
Lines changed: 180 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,180 @@
1+
---
2+
title: 'Tutorial: Azure Active Directory single sign-on (SSO) integration with NS1 SSO for Azure | Microsoft Docs'
3+
description: Learn how to configure single sign-on between Azure Active Directory and NS1 SSO for Azure.
4+
services: active-directory
5+
documentationCenter: na
6+
author: jeevansd
7+
manager: mtillman
8+
ms.reviewer: barbkess
9+
10+
ms.assetid: 24a1afb6-b8b6-4787-bd4b-8fe3a32f8def
11+
ms.service: active-directory
12+
ms.subservice: saas-app-tutorial
13+
ms.workload: identity
14+
ms.tgt_pltfrm: na
15+
ms.topic: tutorial
16+
ms.date: 02/12/2020
17+
ms.author: jeedes
18+
19+
ms.collection: M365-identity-device-management
20+
---
21+
22+
# Tutorial: Azure Active Directory single sign-on (SSO) integration with NS1 SSO for Azure
23+
24+
In this tutorial, you'll learn how to integrate NS1 SSO for Azure with Azure Active Directory (Azure AD). When you integrate NS1 SSO for Azure with Azure AD, you can:
25+
26+
* Control in Azure AD who has access to NS1 SSO for Azure.
27+
* Enable your users to be automatically signed-in to NS1 SSO for Azure with their Azure AD accounts.
28+
* Manage your accounts in one central location - the Azure portal.
29+
30+
To learn more about SaaS app integration with Azure AD, see [What is application access and single sign-on with Azure Active Directory](https://docs.microsoft.com/azure/active-directory/manage-apps/what-is-single-sign-on).
31+
32+
## Prerequisites
33+
34+
To get started, you need the following items:
35+
36+
* An Azure AD subscription. If you don't have a subscription, you can get a [free account](https://azure.microsoft.com/free/).
37+
* NS1 SSO for Azure single sign-on (SSO) enabled subscription.
38+
39+
## Scenario description
40+
41+
In this tutorial, you configure and test Azure AD SSO in a test environment.
42+
43+
* NS1 SSO for Azure supports **SP and IDP** initiated SSO
44+
* Once you configure NS1 SSO for Azure you can enforce session control, which protect exfiltration and infiltration of your organization’s sensitive data in real-time. Session control extend 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).
45+
46+
47+
## Adding NS1 SSO for Azure from the gallery
48+
49+
To configure the integration of NS1 SSO for Azure into Azure AD, you need to add NS1 SSO for Azure from the gallery to your list of managed SaaS apps.
50+
51+
1. Sign in to the [Azure portal](https://portal.azure.com) using either a work or school account, or a personal Microsoft account.
52+
1. On the left navigation pane, select the **Azure Active Directory** service.
53+
1. Navigate to **Enterprise Applications** and then select **All Applications**.
54+
1. To add new application, select **New application**.
55+
1. In the **Add from the gallery** section, type **NS1 SSO for Azure** in the search box.
56+
1. Select **NS1 SSO for Azure** from results panel and then add the app. Wait a few seconds while the app is added to your tenant.
57+
58+
59+
## Configure and test Azure AD single sign-on for NS1 SSO for Azure
60+
61+
Configure and test Azure AD SSO with NS1 SSO for Azure 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 NS1 SSO for Azure.
62+
63+
To configure and test Azure AD SSO with NS1 SSO for Azure, complete the following building blocks:
64+
65+
1. **[Configure Azure AD SSO](#configure-azure-ad-sso)** - to enable your users to use this feature.
66+
1. **[Create an Azure AD test user](#create-an-azure-ad-test-user)** - to test Azure AD single sign-on with B.Simon.
67+
1. **[Assign the Azure AD test user](#assign-the-azure-ad-test-user)** - to enable B.Simon to use Azure AD single sign-on.
68+
1. **[Configure NS1 SSO for Azure SSO](#configure-ns1-sso-for-azure-sso)** - to configure the single sign-on settings on application side.
69+
1. **[Create NS1 SSO for Azure test user](#create-ns1-sso-for-azure-test-user)** - to have a counterpart of B.Simon in NS1 SSO for Azure that is linked to the Azure AD representation of user.
70+
1. **[Test SSO](#test-sso)** - to verify whether the configuration works.
71+
72+
## Configure Azure AD SSO
73+
74+
Follow these steps to enable Azure AD SSO in the Azure portal.
75+
76+
1. In the [Azure portal](https://portal.azure.com/), on the **NS1 SSO for Azure** application integration page, find the **Manage** section and select **single sign-on**.
77+
1. On the **Select a single sign-on method** page, select **SAML**.
78+
1. On the **Set up single sign-on with SAML** page, click the edit/pen icon for **Basic SAML Configuration** to edit the settings.
79+
80+
![Edit Basic SAML Configuration](common/edit-urls.png)
81+
82+
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:
83+
84+
a. In the **Identifier** text box, type the URL:
85+
`https://api.nsone.net/saml/metadata`
86+
87+
b. In the **Reply URL** text box, type a URL using the following pattern:
88+
`https://api.nsone.net/saml/sso/<ssoid>`
89+
90+
1. Click **Set additional URLs** and perform the following step if you wish to configure the application in **SP** initiated mode:
91+
92+
In the **Sign-on URL** text box, type the URL:
93+
`https://my.nsone.net/#/login/sso`
94+
95+
> [!NOTE]
96+
> The Reply URL value is not real. Update Reply URL value with the actual Reply URL. Contact [NS1 SSO for Azure Client support team](mailto:[email protected]) to get the value. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
97+
98+
1. NS1 SSO for Azure application expects the SAML assertions in a specific format. Configure the following claims for this application. You can manage the values of these attributes from the **User Attributes** section on application integration page. On the **Set up Single Sign-On with SAML** page, click **Edit** button to open **User Attributes** dialog.
99+
100+
![Attribute Section](./media/ns1-sso-for-azure-tutorial/attribute-edit-option.png)
101+
102+
1. Click on the attribute name to edit the claim.
103+
104+
![Attribute Section](./media/ns1-sso-for-azure-tutorial/attribute-claim-edit.png)
105+
106+
1. Select **Transformation**.
107+
108+
![Attribute Section](./media/ns1-sso-for-azure-tutorial/prefix-edit.png)
109+
110+
1. On the **Manage transformation** section, perform the following steps:
111+
112+
![Attribute Section](./media/ns1-sso-for-azure-tutorial/prefix-added.png)
113+
114+
1. Select **ExactMailPrefix()** as **Transformation**.
115+
116+
1. Select **user.userprincipalname** as **Parameter 1**.
117+
118+
1. Click on **Add**.
119+
120+
1. Click on **Save**
121+
122+
1. On the **Set up single sign-on with SAML** page, In the **SAML Signing Certificate** section, click copy button to copy **App Federation Metadata Url** and save it on your computer.
123+
124+
![The Certificate download link](common/copy-metadataurl.png)
125+
126+
### Create an Azure AD test user
127+
128+
In this section, you'll create a test user in the Azure portal called B.Simon.
129+
130+
1. From the left pane in the Azure portal, select **Azure Active Directory**, select **Users**, and then select **All users**.
131+
1. Select **New user** at the top of the screen.
132+
1. In the **User** properties, follow these steps:
133+
1. In the **Name** field, enter `B.Simon`.
134+
1. In the **User name** field, enter the [email protected]. For example, `[email protected]`.
135+
1. Select the **Show password** check box, and then write down the value that's displayed in the **Password** box.
136+
1. Click **Create**.
137+
138+
### Assign the Azure AD test user
139+
140+
In this section, you'll enable B.Simon to use Azure single sign-on by granting access to NS1 SSO for Azure.
141+
142+
1. In the Azure portal, select **Enterprise Applications**, and then select **All applications**.
143+
1. In the applications list, select **NS1 SSO for Azure**.
144+
1. In the app's overview page, find the **Manage** section and select **Users and groups**.
145+
146+
![The "Users and groups" link](common/users-groups-blade.png)
147+
148+
1. Select **Add user**, then select **Users and groups** in the **Add Assignment** dialog.
149+
150+
![The Add User link](common/add-assign-user.png)
151+
152+
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.
153+
1. If you're expecting any role value in the SAML assertion, in the **Select Role** dialog, select the appropriate role for the user from the list and then click the **Select** button at the bottom of the screen.
154+
1. In the **Add Assignment** dialog, click the **Assign** button.
155+
156+
## Configure NS1 SSO for Azure SSO
157+
158+
To configure single sign-on on **NS1 SSO for Azure** side, you need to send the **App Federation Metadata Url** to [NS1 SSO for Azure support team](mailto:[email protected]). They set this setting to have the SAML SSO connection set properly on both sides.
159+
160+
### Create NS1 SSO for Azure test user
161+
162+
In this section, you create a user called B.Simon in NS1 SSO for Azure. Work with NS1 SSO for Azure support team to add the users in the NS1 SSO for Azure platform. Users must be created and activated before you use single sign-on.
163+
164+
## Test SSO
165+
166+
In this section, you test your Azure AD single sign-on configuration using the Access Panel.
167+
168+
When you click the NS1 SSO for Azure tile in the Access Panel, you should be automatically signed in to the NS1 SSO for Azure for which you set up SSO. For more information about the Access Panel, see [Introduction to the Access Panel](https://docs.microsoft.com/azure/active-directory/active-directory-saas-access-panel-introduction).
169+
170+
## Additional resources
171+
172+
- [ List of Tutorials on How to Integrate SaaS Apps with Azure Active Directory ](https://docs.microsoft.com/azure/active-directory/active-directory-saas-tutorial-list)
173+
174+
- [What is application access and single sign-on with Azure Active Directory? ](https://docs.microsoft.com/azure/active-directory/manage-apps/what-is-single-sign-on)
175+
176+
- [What is conditional access in Azure Active Directory?](https://docs.microsoft.com/azure/active-directory/conditional-access/overview)
177+
178+
- [Try NS1 SSO for Azure with Azure AD](https://aad.portal.azure.com/)
179+
180+
- [What is session control in Microsoft Cloud App Security?](https://docs.microsoft.com/cloud-app-security/proxy-intro-aad)

0 commit comments

Comments
 (0)