Skip to content

Commit 6f7f5bd

Browse files
authored
Merge pull request #95869 from KingdomOfEnds/adt-refresh
adt refresh
2 parents cb46fde + 78d3908 commit 6f7f5bd

File tree

8 files changed

+8
-17
lines changed

8 files changed

+8
-17
lines changed

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

Lines changed: 6 additions & 15 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: 09/30/2019
10+
ms.date: 11/13/2019
1111
---
1212

1313
# How to configure Postman for Azure Digital Twins
@@ -53,14 +53,9 @@ Configure your Azure Active Directory app to use the OAuth 2.0 implicit grant fl
5353

5454
[![Admin consent approval](../../includes/media/digital-twins-permissions/aad-app-admin-consent.png)](../../includes/media/digital-twins-permissions/aad-app-admin-consent.png#lightbox)
5555

56+
1. Configure a second **Redirect URI** to `https://www.getpostman.com/oauth2/callback`.
5657

57-
1. Select **Manifest** to open the application manifest for your app. Set *oauth2AllowImplicitFlow* to `true`.
58-
59-
[![Azure Active Directory implicit flow](media/how-to-configure-postman/implicit-flow.png)](media/how-to-configure-postman/implicit-flow.png#lightbox)
60-
61-
1. Configure a **Reply URL** to `https://www.getpostman.com/oauth2/callback`.
62-
63-
[![Azure Active Directory Reply URL](media/how-to-configure-postman/reply-url.png)](media/how-to-configure-postman/reply-url.png#lightbox)
58+
[![Add a Postman Redirect URI](media/how-to-configure-postman/authentication-redirect-uri.png)](media/how-to-configure-postman/authentication-redirect-uri.png#lightbox)
6459

6560
1. Copy and keep the **Application ID** of your Azure Active Directory app. It's used in the steps that follow.
6661

@@ -101,24 +96,20 @@ Set up and configure Postman to obtain an Azure Active Directory token. Afterwar
10196
[![Postman client example](media/how-to-configure-postman/postman-oauth-token.png)](media/how-to-configure-postman/postman-oauth-token.png#lightbox)
10297
10398
1. Select **Request Token**.
104-
105-
>[!TIP]
106-
>If you receive the error message "OAuth 2 couldn’t be completed," try the following:
107-
> * Close Postman, and reopen it and try again.
10899
109100
1. Scroll down, and select **Use Token**.
110101
111102
## Make a multipart POST request
112103
113104
After completing the previous steps, configure Postman to make an authenticated HTTP multipart POST request:
114105
115-
1. Under the **Header** tab, add an HTTP request header key **Content-Type** with value `multipart/mixed`.
106+
1. Under the **Headers** tab, add an HTTP request header key **Content-Type** with value `multipart/mixed`.
116107
117108
[![Content type multipart/mixed](media/how-to-configure-postman/content-type.png)](media/how-to-configure-postman/content-type.png#lightbox)
118109
119110
1. Serialize non-text data into files. JSON data would be saved as a JSON file.
120111
1. Under the **Body** tab, select `form-data`.
121-
1. Add each file by assigning a **key** name, selecting `file`.
112+
1. Add each file by assigning a **key** name, selecting `File`.
122113
1. Then, select each file through the **Choose File** button.
123114
124115
[![Postman client example](media/how-to-configure-postman/form-body.png)](media/how-to-configure-postman/form-body.png#lightbox)
@@ -128,7 +119,7 @@ After completing the previous steps, configure Postman to make an authenticated
128119
> * You do not need to specify those headers for each part.
129120
> * You must select `multipart/mixed` or another appropriate **Content-Type** for the entire request.
130121
131-
1. Lastly, select **Send** to submit your multipart HTTP POST request.
122+
1. Lastly, select **Send** to submit your multipart HTTP POST request. A status code of `200` or `201` indicates a successful request. You will also see the appropriate response message.
132123
133124
## Next steps
134125
97.6 KB
Loading
40.1 KB
Loading
94.8 KB
Loading
Binary file not shown.
31.8 KB
Loading
Binary file not shown.

includes/digital-twins-familiarity.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,11 +7,11 @@
77
manager: bertvanhoof
88
ms.service: digital-twins
99
ms.topic: include
10-
ms.date: 10/02/2019
10+
ms.date: 11/13/2019
1111
ms.custom: include file
1212
---
1313

14-
This article assumes some familiarity authenticating with your Azure Digital Twins Management APIs.
14+
This article assumes some familiarity with authenticating to your Azure Digital Twins Management APIs.
1515

1616
* To learn more about authenticating with your Management APIs, see [Authenticating with Azure Digital Twins APIs](../articles/digital-twins/security-authenticating-apis.md).
1717
* To authenticate with your Management APIs using the Postman REST client, read [How to configure Postman](../articles/digital-twins/how-to-configure-postman.md).

0 commit comments

Comments
 (0)