You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/energy-data-services/how-to-generate-auth-token.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ In this article, you learn how to generate the service principal auth token, a u
17
17
## Register your app with Microsoft Entra ID
18
18
19
19
1. To provision the Azure Data Manager for Energy platform, you must register your app on the [Azure portal app registration page](https://go.microsoft.com/fwlink/?linkid=2083908). You can use either a Microsoft account or a work or school account to register an app. For steps on how to configure, see [Register your app documentation](../active-directory/develop/quickstart-register-app.md#register-an-application).
20
-
1. In the app overview section, if there are no redirect URIsspecified, you can select **Add a platform** > **Web**, add `http://localhost:8080`, and select **Save**.
20
+
1. In the application overview section, if no redirect Uniform Resource Identifiers (URIs) are specified, select **Add a platform** > **Web**, add `http://localhost:8080`, and then select **Save**.
21
21
22
22
:::image type="content" source="media/how-to-generate-auth-token/app-registration-uri.png" alt-text="Screenshot that shows adding the URI to the app.":::
23
23
@@ -38,7 +38,7 @@ You can also find the parameters after the app is registered on the Azure portal
38
38
39
39
### Find client-id
40
40
41
-
A `client-id` is the same value that you use to register your application during the provisioning of your [Azure Data Manager for Energy instance](quickstart-create-microsoft-energy-data-services-instance.md). It's often referred to as `app-id`.
41
+
A `client-id` is the value used to register your application during the provisioning of your [Azure Data Manager for Energy instance](quickstart-create-microsoft-energy-data-services-instance.md). It is often referred to as `app-id`.
42
42
43
43
1. Go to the Azure Data Manager for Energy **Overview** page. On the **Essentials** pane, find **client ID**.
44
44
1. Copy the `client-id` value and paste it into an editor to be used later.
@@ -51,7 +51,7 @@ A `client-id` is the same value that you use to register your application during
51
51
52
52
### Find client-secret
53
53
54
-
A `client-secret` is a string value your app can use in place of a certificate to identify itself. It's sometimes referred to as an application password.
54
+
A `client-secret` is a string value your app can use in place of a certificate to identify itself. It is sometimes called an application password.
55
55
56
56
1. Go to **App registrations**.
57
57
1. Under the **Manage** section, select **Certificates & secrets**.
@@ -76,7 +76,7 @@ The `redirect-uri` of your app, where your app sends and receives the authentica
76
76
77
77
### Find the adme-url for your Azure Data Manager for Energy instance
78
78
79
-
1. Create an [Azure Data Manager for Energy instance](quickstart-create-microsoft-energy-data-services-instance.md) using the `client-id`generated above.
79
+
1.Create an [Azure Data Manager for Energy instance](quickstart-create-microsoft-energy-data-services-instance.md) using the `client-id`obtained in the [Find client-id](#find-client-id) section.
80
80
1. Go to your Azure Data Manager for Energy **Overview** page on the Azure portal.
81
81
1. On the **Essentials** pane, copy the URI.
82
82
@@ -159,11 +159,11 @@ The first step to get an access token for many OpenID Connect (OIDC) and OAuth 2
159
159
|Parameter| Description|
160
160
| --- | --- |
161
161
|code|The authorization code that the app requested. The app can use the authorization code to request an access token for the target resource. Authorization codes are short lived. Typically, they expire after about 10 minutes.|
162
-
|state|If a state parameter is included in the request, the same value should appear in the response. The app should verify that the state values in the request and response are identical. This check helps to detect [CSRF attacks](https://tools.ietf.org/html/rfc6749#section-10.12) against the client.|
162
+
|state|If a state parameter is included in the request, the same value should appear in the response. The app should verify that the state values in the request and response are identical. This check helps to detect Cross-Site Request Forgery (CSRF) attacks. For more information, see [CSRF attacks](https://tools.ietf.org/html/rfc6749#section-10.12).|
163
163
|session_state|A unique value that identifies the current user session. This value is a GUID, but it should be treated as an opaque value that's passed without examination.|
164
164
165
165
> [!WARNING]
166
-
> Running the URL in Postman won't work because it requires extra configuration for token retrieval.
166
+
> Running the URL in other GUI-based API clients doesn't work because they require extra configuration for token retrieval.
Copy file name to clipboardExpand all lines: articles/energy-data-services/tutorial-seismic-ddms.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -284,4 +284,5 @@ As an alternative user experience to Postman, you can use the sdutil command-lin
284
284
> [!div class="nextstepaction"]
285
285
> [Use sdutil to load data into Seismic Store](./tutorial-seismic-ddms-sdutil.md)
286
286
>
287
-
> For more information on the Seismic REST APIs in Azure Data Manager for Energy, see the OpenAPI specifications available in the [adme-samples](https://microsoft.github.io/adme-samples/) GitHub repository.
287
+
288
+
For more information on the Seismic REST APIs in Azure Data Manager for Energy, see the OpenAPI specifications available in the [adme-samples](https://microsoft.github.io/adme-samples/) GitHub repository.
0 commit comments