Skip to content

Commit b4c7a91

Browse files
committed
updated aad
1 parent bf3a158 commit b4c7a91

12 files changed

+32
-50
lines changed

articles/digital-twins/how-to-configure-postman.md

Lines changed: 7 additions & 37 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ manager: bertvanhoof
77
ms.service: digital-twins
88
services: digital-twins
99
ms.topic: conceptual
10-
ms.date: 01/10/2020
10+
ms.date: 02/03/2020
1111
---
1212

1313
# How to configure Postman for Azure Digital Twins
@@ -28,45 +28,17 @@ Through the Postman client, solutions developers can specify the kind of HTTP re
2828

2929
## Configure Azure Active Directory to use the OAuth 2.0 implicit grant flow
3030

31-
Configure your Azure Active Directory app to use the OAuth 2.0 implicit grant flow.
31+
1. Follow the steps in [the Quickstart](quickstart-view-occupancy-dotnet.md#set-permissions-for-your-app) to create and configure an Azure Active Directory application. Alternatively, you can reuse an existing app registration.
3232

33-
1. Open the **API permissions** pane for your app registration. Select **Add a permission** button. In the **Request API permissions** pane, select the **APIs my organization uses** tab, and then search for:
34-
35-
1. `Azure Digital Twins`. Select the **Azure Digital Twins** API.
36-
37-
[![Search API or Azure Digital Twins](../../includes/media/digital-twins-permissions/aad-aap-search-api-dt.png)](../../includes/media/digital-twins-permissions/aad-aap-search-api-dt.png#lightbox)
38-
39-
1. Alternatively, search for `Azure Smart Spaces Service`. Select the **Azure Smart Spaces Service** API.
40-
41-
[![Search API for Azure Smart Spaces](../../includes/media/digital-twins-permissions/aad-app-search-api.png)](../../includes/media/digital-twins-permissions/aad-app-search-api.png#lightbox)
42-
43-
> [!IMPORTANT]
44-
> The Azure AD API name and ID that will appear depends on your tenant:
45-
> * Test tenant and customer accounts should search for `Azure Digital Twins`.
46-
> * Other Microsoft accounts should search for `Azure Smart Spaces Service`.
47-
48-
1. The selected API shows up as **Azure Digital Twins** in the same **Request API permissions** pane. Select the **Read (1)** drop down, and then select **Read.Write** checkbox. Select the **Add permissions** button.
49-
50-
[![Add API permissions for Azure Digital Twins](../../includes/media/digital-twins-permissions/aad-app-req-permissions.png)](../../includes/media/digital-twins-permissions/aad-app-req-permissions.png#lightbox)
51-
52-
1. Depending on your organization's settings, you might need to take additional steps to grant admin access to this API. Contact your administrator for more information. Once the admin access is approved, the **ADMIN CONSENT REQUIRED** column in the **API permissions** pane will show similar to the following for your APIs:
53-
54-
[![Configure admin consent approval](../../includes/media/digital-twins-permissions/aad-app-admin-consent.png)](../../includes/media/digital-twins-permissions/aad-app-admin-consent.png#lightbox)
55-
56-
1. Configure a second **Redirect URI** to `https://www.getpostman.com/oauth2/callback`.
33+
1. Add a **Redirect URI** to `https://www.getpostman.com/oauth2/callback`.
5734

5835
[![Configure a new Postman Redirect URI](media/how-to-configure-postman/authentication-redirect-uri.png)](media/how-to-configure-postman/authentication-redirect-uri.png#lightbox)
5936

60-
1. To make sure that [the app is registered as a **public client**](https://docs.microsoft.com/azure/active-directory/develop/scenario-desktop-app-registration), open the **Authentication** pane for your app registration, and scroll down in that pane. In the **Default client type** section, choose **Yes** for **Treat application as a public client**, and hit **Save**.
61-
62-
Check **Access tokens** to enable the **oauth2AllowImplicitFlow** setting in your Manifest.json.
37+
1. Select the **Implicit grant** > **Access tokens** check box to allow the OAuth 2.0 implicit grant flow to be used.
6338

64-
[![Public client configuration setting](../../includes/media/digital-twins-permissions/aad-configure-public-client.png)](../../includes/media/digital-twins-permissions/aad-configure-public-client.png#lightbox)
65-
66-
1. Copy and keep the **Application ID** of your Azure Active Directory app. It's used in the steps that follow.
67-
68-
[![Azure Active Directory application ID](../../includes/media/digital-twins-permissions/aad-app-reg-app-id.png)](../../includes/media//digital-twins-permissions/aad-app-reg-app-id.png#lightbox)
39+
1. Select **Configure**, then **Save**.
6940

41+
1. Copy the **Client ID** of your Azure Active Directory app.
7042

7143
## Obtain an OAuth 2.0 token
7244

@@ -86,15 +58,13 @@ Set up and configure Postman to obtain an Azure Active Directory token. Afterwar
8658
8759
1. Go to [www.getpostman.com](https://www.getpostman.com/) to download the app.
8860
89-
1. Open the Postman app and click new | Create new, and select Request. Enter a Request name. Select a collection or folder to save it to, and click Save.
90-
9161
1. We want to make GET request. Select the **Authorization** tab, select OAuth 2.0, and then select **Get New Access Token**.
9262
9363
| Field | Value |
9464
|---------|---------|
9565
| Grant Type | `Implicit` |
9666
| Callback URL | `https://www.getpostman.com/oauth2/callback` |
97-
| Auth URL | Use the **Authorization URL** from **step 2** |
67+
| Auth URL | Use the **Authorization URL** from **step 1** |
9868
| Client ID | Use the **Application ID** for the Azure Active Directory app that was created or reused from the previous section |
9969
| Scope | Leave blank |
10070
| State | Leave blank |

articles/digital-twins/how-to-use-swagger.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ manager: bertvanhoof
77
ms.service: digital-twins
88
services: digital-twins
99
ms.topic: conceptual
10-
ms.date: 01/21/2020
10+
ms.date: 02/03/2020
1111
ms.custom: seodec18
1212
---
1313

@@ -90,9 +90,9 @@ The examples also include error codes to help debug or improve failing tests.
9090
> [!NOTE]
9191
> * The user principal that created the Azure Digital Twins resource will have a Space Administrator role assignment and will be able to create additional role assignments for other users. Such users and their roles can be authorized to call the APIs.
9292
93-
1. Follow the steps in [this quickstart](https://docs.microsoft.com/azure/active-directory/develop/quickstart-v1-integrate-apps-with-azure-ad) to create and configure an Azure AD application. Alternatively, you can reuse an existing app registration.
93+
1. Follow the steps in [the Quickstart](quickstart-view-occupancy-dotnet.md#set-permissions-for-your-app) to create and configure an Azure Active Directory application. Alternatively, you can reuse an existing app registration.
9494

95-
1. Add the following **Redirect url** to your Azure AD app registration:
95+
1. Add the following **Redirect URI** to your Azure Active Directory app registration:
9696

9797
[![Register Swagger redirect url in AAD](media/how-to-use-swagger/swagger-aad-redirect-url-registration.png)](media/how-to-use-swagger/swagger-aad-redirect-url-registration.png#lightbox)
9898

@@ -103,7 +103,9 @@ The examples also include error codes to help debug or improve failing tests.
103103
|---------|---------|---------|
104104
| YOUR_SWAGGER_URL | Your Management REST API documentation URL found in the portal | `https://yourDigitalTwinsName.yourLocation.azuresmartspaces.net/management/swagger` |
105105
106-
1. Copy the **Client ID** of your Azure AD app.
106+
1. Select the **Implicit grant** > **Access tokens** check box to allow the OAuth 2.0 implicit grant flow to be used. Select **Configure**, then **Save**.
107+
108+
1. Copy the **Client ID** of your Azure Active Directory app.
107109
108110
After completing the Azure Active Directory registration:
109111
254 KB
Loading
110 KB
Loading

includes/digital-twins-permissions.md

Lines changed: 19 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@
77
manager: bertvanhoof
88
ms.service: digital-twins
99
ms.topic: include
10-
ms.date: 01/23/2020
10+
ms.date: 02/03/2020
1111
ms.custom: include file
1212
---
1313

@@ -26,20 +26,30 @@
2626

2727
[![Create pane](./media/digital-twins-permissions/aad-app-reg-create.png)](./media/digital-twins-permissions/aad-app-reg-create.png#lightbox)
2828

29-
1. To make sure that [the app is registered as a **public client**](https://docs.microsoft.com/azure/active-directory/develop/scenario-desktop-app-registration), open the **Authentication** pane for your app registration, and scroll down in that pane. In the **Default client type** section, choose **Yes** for **Treat application as a public client**, and hit **Save**.
29+
1. The **Authentication** blade specifies important authentication configuration settings.
3030

31-
1. **Redirect URIs** must match the address supplied by the authentication request:
31+
1. Add **Redirect URIs** and configure **Access Tokens** by selecting **+ Add a platform**.
32+
33+
1. Determine whether the app is a **public client** or not by selecting **Yes** or **No**.
34+
35+
1. Verify which accounts and tenants are supported.
3236

33-
* For apps hosted in a local development environment, select **Public client (mobile & desktop)**. Make sure to set the **Default client type** to yes.
34-
* For Single-Page apps hosted on Azure App Service, select **Web**.
37+
[![Public client configuration setting](./media/digital-twins-permissions/aad-configure-public-client.png)](./media/digital-twins-permissions/aad-configure-public-client.png#lightbox)
38+
39+
1. After selecting the appropriate platform, configure your **Redirect URIs** and **Access Tokens** in the side panel to the right of the user interface.
40+
41+
1. **Redirect URIs** must match the address supplied by the authentication request:
3542

36-
Select **Public client (mobile & desktop)** and enter `http://localhost:8080/`.
43+
* For apps hosted in a local development environment, select **Public client (mobile & desktop)**. Make sure to set **public client** to **Yes**.
44+
* For Single-Page Apps hosted on Azure App Service, select **Web**.
3745

38-
[![Configure Redirect URIs](./media/digital-twins-permissions/aad-app-configure-redirect-uris.png)](./media/digital-twins-permissions/aad-app-configure-redirect-uris.png#lightbox)
46+
1. Determine whether a **Logout URL** is appropriate.
3947

40-
1. Check **Access tokens** to configure the **oauth2AllowImplicitFlow** setting to `true` in your resource's **Manifest** JSON.
48+
1. Enable the implicit grant flow by checking **Access tokens** or **ID tokens**.
49+
50+
[![Configure Redirect URIs](./media/digital-twins-permissions/aad-app-configure-redirect-uris.png)](./media/digital-twins-permissions/aad-app-configure-redirect-uris.png#lightbox)
4151

42-
[![Public client configuration setting](./media/digital-twins-permissions/aad-configure-public-client.png)](./media/digital-twins-permissions/aad-configure-public-client.png#lightbox)
52+
Click **Configure**, then **Save**.
4353

4454
1. Open the **Overview** pane of your registered app, and copy the values of the following entities to a temporary file. You'll use these values to configure your sample application in the following sections.
4555

74.6 KB
Loading
67.1 KB
Loading
-85.3 KB
Loading
75.1 KB
Loading
-2.5 KB
Loading

0 commit comments

Comments
 (0)