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/active-directory-b2c/identity-provider-apple-id.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -110,7 +110,7 @@ If the sign-in process is successful, your browser is redirected to `https://jwt
110
110
111
111
## Signing the client secret
112
112
113
-
Use the .p8 file you downloaded previously to sign the client secret into a JWT token. There are many libraries that can create and sign the JWT for you. Use the [Azure Function that creates a token](https://github.com/azure-ad-b2c/samples/tree/master/policies/sign-in-with-apple/azure-function) for you.
113
+
Use the .p8 file you downloaded previously to sign the client secret into a JWT. There are many libraries that can create and sign the JWT for you. Use the [Azure Function that creates a token](https://github.com/azure-ad-b2c/samples/tree/master/policies/sign-in-with-apple/azure-function) for you.
114
114
115
115
1. Create an [Azure Function](../azure-functions/functions-create-function-app-portal.md).
116
116
1. Under **Developer**, select **Code + Test**.
@@ -154,7 +154,7 @@ You need to store the client secret that you previously recorded in your Azure A
154
154
1. Select **Policy Keys**, and then select **Add**.
155
155
1. For **Options**, choose **Manual**.
156
156
1. Enter a **Name** for the policy key. For example, "AppleSecret". The prefix "B2C_1A_" is added automatically to the name of your key.
157
-
1. In **Secret**, enter the value of a token returned by the Azure Function (a JWT token).
157
+
1. In **Secret**, enter the value of a token returned by the Azure Function (a JWT).
Copy file name to clipboardExpand all lines: articles/active-directory-b2c/troubleshoot.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -155,11 +155,11 @@ The following screenshot shows an example of the Application Insights trace log
155
155
156
156
157
157
158
-
## Troubleshoot JWT tokens
158
+
## Troubleshoot JWTs
159
159
160
-
For JWT token validation and debugging purposes, your can decode JWTs using a site like [https://jwt.ms](https://jwt.ms). Create a test application that can redirect to `https://jwt.ms` for token inspection. If you haven't already done so, [register a web application](tutorial-register-applications.md), and [enable ID token implicit grant](tutorial-register-applications.md#enable-id-token-implicit-grant).
160
+
For JWT validation and debugging purposes, your can decode JWTs using a site like [https://jwt.ms](https://jwt.ms). Create a test application that can redirect to `https://jwt.ms` for token inspection. If you haven't already done so, [register a web application](tutorial-register-applications.md), and [enable ID token implicit grant](tutorial-register-applications.md#enable-id-token-implicit-grant).
161
161
162
-
162
+
163
163
164
164
Use **Run now** and `https://jwt.ms` to test your policies independently of your web or mobile application. This website acts like a relying party application. It displays the contents of the JSON web token (JWT) that your Azure AD B2C policy generates.
Copy file name to clipboardExpand all lines: articles/app-service/monitor-instances-health-check.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -143,11 +143,11 @@ function envVarMatchesHeader(headerValue) {
143
143
144
144
## Instances
145
145
146
-
Once Health check is enabled, you can restart and monitor the status of your application instances from the instances tab. The instances tab shows your instance's name and the status of that application's instance. You can also manually restart the instance from this tab.
146
+
Once Health check is enabled, you can restart and monitor the status of your application instances from the instances tab. The instances tab shows your instance's name and the status of that application's instance. You can also manually do an advanced application restart from this tab by using the "Restart" button.
147
147
148
-
If the status of your application instance is "unhealthy," you can restart the instance manually by using the restart button in the table. Keep in mind that any other applications hosted on the same App Service plan as the instance will also be affected by the restart. If there are other applications using the same App Service plan as the instance, they're listed on the opening blade from the restart button.
148
+
If the status of your application instance is "unhealthy," you can restart the worker process of the respective app manually by using the restart button in the table. This will not be affecting any of the other applications hosted on the same App Service plan. If there are other applications using the same App Service plan as the instance, they're listed on the opening blade from the restart button.
149
149
150
-
If you restart the instance and the restart process fails, you'll be given the option to replace the worker. (Only one instance can be replaced per hour.) This will also affect any applications using the same App Service plan.
150
+
If you restart the instance and the restart process fails, you'll be given the option to replace the worker. (Only one instance can be replaced per hour.) This will affect any applications using the same App Service plan.
151
151
152
152
For Windows applications, you can also view processes via the Process Explorer. This gives you further insight on the instance's processes, including thread count, private memory, and total CPU time.
Copy file name to clipboardExpand all lines: articles/azure-web-pubsub/concept-service-internals.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -197,7 +197,7 @@ The maximum allowed message size for one WebSocket frame is **1MB**.
197
197
198
198
#### Authentication workflow
199
199
200
-
Client uses a signed JWT token to connect to the service. The upstream can also reject the client when it's `connect` event handler of the incoming client. The event handler authenticates the client by specifying the `userId` and the `role`s the client has in the webhook response, or decline the client with 401. [Event handler](#event-handler) section describes it in detail.
200
+
Client uses a signed JSON Web Token (JWT) to connect to the service. The upstream can also reject the client when it's `connect` event handler of the incoming client. The event handler authenticates the client by specifying the `userId` and the `role`s the client has in the webhook response or decline the client with 401. [Event handler](#event-handler) section describes it in detail.
Copy file name to clipboardExpand all lines: articles/azure-web-pubsub/howto-connect-mqtt-websocket-client.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -59,10 +59,10 @@ This is the default workflow, shown as follows:
59
59
60
60
1. The client negotiates with your auth server. The auth server contains the authorization middleware, which handles the client request and signs a JWT for the client to connect to the service.
61
61
1. The auth server returns the JWT to the client.
62
-
1. The client tries to connect to the Web PubSub service with the JWT token returned from the auth server. The token can be in either the query string, as `/clients/mqtt/hubs/{hub}?access_token={token}`, or the `Authorization` header, as `Authorization: Bearer {token}`.
62
+
1. The client tries to connect to the Web PubSub service with the JWT returned from the auth server. The token can be in either the query string, as `/clients/mqtt/hubs/{hub}?access_token={token}`, or the `Authorization` header, as `Authorization: Bearer {token}`.
63
63
64
64
#### Supported claims
65
-
You could also configure properties for the client connection when generating the access token by specifying special claims inside the JWT token:
65
+
You could also configure properties for the client connection when generating the access token by specifying special claims inside the JWT:
66
66
67
67
| Description | Claim type | Claim value | Notes |
0 commit comments