Skip to content

Commit da911e1

Browse files
authored
rwike feedback
Thanks @rwike77 !
1 parent 4d06f5f commit da911e1

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/active-directory/develop/reference-aadsts-error-codes.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -28,12 +28,12 @@ Looking for info about the AADSTS error codes that are returned from the Azure A
2828

2929
The [OAuth2.0 spec](https://tools.ietf.org/html/rfc6749#section-5.2) provides guidance on how to handle errors during authentication using the `error` portion of the error response.
3030

31-
Error responses will look like:
31+
Here is a sample error response:
3232

3333
```json
3434
{
3535
"error": "invalid_scope",
36-
"error_description": "AADSTS70011: The provided value for the input parameter 'scope' is not valid. The scope https://foo.microsoft.com/mail.read is not valid.\r\nTrace ID: 255d1aef-8c98-452f-ac51-23d051240864\r\nCorrelation ID: fb3d2015-bc17-4bb9-bb85-30c5cf1aaaa7\r\nTimestamp: 2016-01-09 02:02:12Z",
36+
"error_description": "AADSTS70011: The provided value for the input parameter 'scope' is not valid. The scope https://example.contoso.com/activity.read is not valid.\r\nTrace ID: 255d1aef-8c98-452f-ac51-23d051240864\r\nCorrelation ID: fb3d2015-bc17-4bb9-bb85-30c5cf1aaaa7\r\nTimestamp: 2016-01-09 02:02:12Z",
3737
"error_codes": [
3838
70011
3939
],
@@ -47,14 +47,14 @@ Error responses will look like:
4747
| Parameter | Description |
4848
|-------------------|----------------|
4949
| `error` | An error code string that can be used to classify types of errors that occur, and should be used to react to errors. |
50-
| `error_description` | A specific error message that can help a developer identify the root cause of an authentication error. Should never be used by your code to react to an error. |
50+
| `error_description` | A specific error message that can help a developer identify the root cause of an authentication error. Never use this field to react to an error in your code. |
5151
| `error_codes` | A list of STS-specific error codes that can help in diagnostics. |
5252
| `timestamp` | The time at which the error occurred. |
5353
| `trace_id` | A unique identifier for the request that can help in diagnostics. |
5454
| `correlation_id` | A unique identifier for the request that can help in diagnostics across components. |
5555
| `error_uri` | A link to the error lookup page with additional information about the error. This is for developer usage only, do not present it to users. Only present when the error lookup system has additional information about the error - not all error have additional information provided.|
5656

57-
The `error` field has several possible values - review the protocol documentation links to learn more about specific errors (e.g. `authorization_pending` for the [device code flow](v2-oauth2-device-code.md)) and how to react to them. Some common ones are listed here:
57+
The `error` field has several possible values - review the protocol documentation links and OAuth 2.0 specs to learn more about specific errors (for example, `authorization_pending` in the [device code flow](v2-oauth2-device-code.md)) and how to react to them. Some common ones are listed here:
5858

5959
| Error Code | Description | Client Action |
6060
|--------------------|--------------------|------------------|

0 commit comments

Comments
 (0)