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/whats-new-docs.md
+11-7Lines changed: 11 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: "What's new in Azure Active Directory business-to-customer (B2C)"
3
3
description: "New and updated documentation for the Azure Active Directory business-to-customer (B2C)."
4
-
ms.date: 10/01/2024
4
+
ms.date: 11/04/2024
5
5
ms.service: azure-active-directory
6
6
ms.subservice: b2c
7
7
ms.topic: whats-new
@@ -19,6 +19,16 @@ manager: CelesteDG
19
19
20
20
Welcome to what's new in Azure Active Directory B2C documentation. This article lists new docs that have been added and those that have had significant updates in the last three months. To learn what's new with the B2C service, see [What's new in Microsoft Entra ID](../active-directory/fundamentals/whats-new.md), [Azure AD B2C developer release notes](custom-policy-developer-notes.md) and [What's new in Microsoft Entra External ID](/entra/external-id/whats-new-docs).
21
21
22
+
## October 2024
23
+
24
+
### Updated articles
25
+
26
+
-[Secure APIs used for API connectors in Azure AD B2C](secure-rest-api.md) - ROPC flow updates
27
+
-[Application types that can be used in Active Directory B2C](application-types.md) - Implicit grant flow updates
28
+
-[Configure authentication in a sample single-page application by using Azure AD B2C](configure-authentication-sample-spa-app.md) - Implicit grant flow updates
29
+
-[Single-page application sign-in using the OAuth 2.0 implicit flow in Azure Active Directory B2C](implicit-flow-single-page-application.md) - Implicit grant flow updates
30
+
-[Register a single-page application in Azure Active Directory B2C](tutorial-register-spa.md) - Implicit grant flow updates
31
+
22
32
## September 2024
23
33
24
34
### Updated articles
@@ -33,9 +43,3 @@ This month, we changed Twitter to X in numerous articles and code samples.
33
43
34
44
-[Tutorial: Configure Keyless with Azure Active Directory B2C](partner-keyless.md) - Editorial updates
35
45
36
-
## July 2024
37
-
38
-
### Updated articles
39
-
40
-
-[Developer notes for Azure Active Directory B2C](custom-policy-developer-notes.md) - Updated Twitter to X
41
-
-[Custom email verification with SendGrid](custom-email-sendgrid.md) - Updated the localization script
Copy file name to clipboardExpand all lines: articles/api-management/api-management-howto-api-inspector.md
+35-20Lines changed: 35 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ services: api-management
5
5
author: dlepow
6
6
ms.service: azure-api-management
7
7
ms.topic: tutorial
8
-
ms.date: 05/05/2024
8
+
ms.date: 11/04/2024
9
9
ms.author: danlep
10
10
ms.custom: devdivchpfy22
11
11
---
@@ -36,11 +36,14 @@ In this tutorial, you learn how to:
36
36
37
37
## Trace a call in the portal
38
38
39
+
Follow these steps to trace an API request in the test console in the portal. This example assumes that you [imported](import-and-publish.md) a sample API in a previous tutorial. You can follow similar steps with a different API that you imported.
40
+
39
41
1. Sign in to the [Azure portal](https://portal.azure.com), and navigate to your API Management instance.
40
-
1. Select **APIs**.
41
-
1. Select **Demo Conference API** from your API list.
42
+
1. Select **APIs** > **APIs**.
43
+
1. Select **Petstore API** from your API list.
42
44
1. Select the **Test** tab.
43
-
1. Select the **GetSpeakers** operation.
45
+
1. Select the **Find pet by ID** operation.
46
+
1. In the *petId***Query parameter**, enter *1*.
44
47
1. Optionally check the value for the **Ocp-Apim-Subscription-Key** header used in the request by selecting the "eye" icon.
45
48
> [!TIP]
46
49
> You can override the value of **Ocp-Apim-Subscription-Key** by retrieving a key for another subscription in the portal. Select **Subscriptions**, and open the context menu (**...**) for another subscription. Select **Show/hide keys** and copy one of the keys. You can also regenerate keys if needed. Then, in the test console, select **+ Add header** to add an **Ocp-Apim-Subscription-Key** header with the new key value.
@@ -55,7 +58,7 @@ In this tutorial, you learn how to:
***Inbound** - Shows the original request API Management received from the caller and the policies applied to the request. For example, if you added policies in [Tutorial: Transform and protect your API](transform-api.md), they'll appear here.
61
+
***Inbound** - Shows the original request API Management received from the caller and the policies applied to the request. For example, if you added policies in [Tutorial: Transform and protect your API](transform-api.md), they appear here.
59
62
60
63
***Backend** - Shows the requests API Management sent to the API backend and the response it received.
61
64
@@ -69,25 +72,31 @@ In this tutorial, you learn how to:
69
72
70
73
## Enable tracing for an API
71
74
72
-
You can enable tracing for an API when making requests to API Management using `curl`, a REST client such as Visual Studio Code with the REST Client extension, or a client app.
75
+
The following high level steps are required to enable tracing for a request to API Management when using `curl`, a REST client such as Visual Studio Code with the REST Client extension, or a client app. Currently these steps must be followed using the [API Management REST API](/rest/api/apimanagement):
76
+
77
+
1. Obtain a token credential for tracing.
78
+
1. Add the token value in an `Apim-Debug-Authorization` request header to the API Management gateway.
79
+
1. Obtain a trace ID in the `Apim-Trace-Id` response header.
80
+
1. Retrieve the trace corresponding to the trace ID.
73
81
74
-
Enable tracing by the following steps using calls to the API Management REST API.
82
+
Detailed steps follow.
75
83
76
84
> [!NOTE]
77
-
> The following steps require API Management REST API version 2023-05-01-preview or later. You must be assigned the Contributor or higher role on the API Management instance to call the REST API.
85
+
> * These steps require API Management REST API version 2023-05-01-preview or later. You must be assigned the Contributor or higher role on the API Management instance to call the REST API.
86
+
> * For information about authenticating to the REST API, see [Azure REST API reference](/rest/api/azure).
78
87
79
-
1. Obtain trace credentials by calling the [List debug credentials](/rest/api/apimanagement/gateway/list-debug-credentials) API. Pass the gateway ID in the URI, or use "managed" for the instance's managed gateway in the cloud. For example, to obtain trace credentials for the managed gateway, use a call similar to the following:
88
+
1.**Obtain a token credential** - Call the API Management gateway's [List debug credentials](/rest/api/apimanagement/gateway/list-debug-credentials) API. In the URI, enter "managed" for the instance's managed gateway in the cloud, or the gateway ID for a self-hosted gateway. For example, to obtain trace credentials for the instance's managed gateway, use a request similar to the following:
80
89
81
90
```http
82
91
POST https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ApiManagement/service/{serviceName}/gateways/managed/listDebugCredentials?api-version=2023-05-01-preview
83
92
```
84
93
85
-
In the request body, pass the full resource ID of the API that you want to trace, and specify `purposes` as `tracing`. By default the token credential returned in the response expires after 1 hour, but you can specify a different value in the payload.
94
+
In the request body, pass the full resource ID of the API that you want to trace, and specify `purposes` as `tracing`. By default the token credential returned in the response expires after 1 hour, but you can specify a different value in the payload. For example:
@@ -96,21 +105,27 @@ Enable tracing by the following steps using calls to the API Management REST API
96
105
97
106
```json
98
107
{
99
-
"token": "aid=api-name&p=tracing&ex=......."
108
+
"token": "aid=api-name&......."
100
109
}
101
110
```
102
111
103
-
1. To enable tracing for a request to the API Management gateway, send the token value in an `Apim-Debug-Authorization` header. For example, to trace a call to the demo conference API, use a call similar to the following:
112
+
1. **Add the token value in a request header** - To enable tracing for a request to the API Management gateway, send the token value in an `Apim-Debug-Authorization` header. For example, to trace a call to the Petstore API that you imported in a previous tutorial, you might use a request similar to the following:
1. Depending on the token, the response contains different headers:
109
-
* If the token is valid, the response includes an `Apim-Trace-Id` header whose value is the trace ID.
117
+
118
+
1. Depending on the token, the response contains one of the following headers:
119
+
* If the token is valid, the response includes an `Apim-Trace-Id` header whose value is the trace ID, similar to the following:
120
+
121
+
```http
122
+
Apim-Trace-Id: 0123456789abcdef....
123
+
```
124
+
110
125
* If the token is expired, the response includes an `Apim-Debug-Authorization-Expired` header with information about expiration date.
111
-
* If the token was obtained for wrong API, the response includes an `Apim-Debug-Authorization-WrongAPI` header with an error message.
126
+
* If the token was obtained for a different API, the response includes an `Apim-Debug-Authorization-WrongAPI` header with an error message.
112
127
113
-
1. To retrieve the trace, pass the trace ID obtained in the previous step to the [List trace](/rest/api/apimanagement/gateway/list-trace) API for the gateway. For example, to retrieve the trace for the managed gateway, use a call similar to the following:
128
+
1. **Retrieve the trace** - Pass the trace ID obtained in the previous step to the gateway's [List trace](/rest/api/apimanagement/gateway/list-trace) API. For example, to retrieve the trace for the managed gateway, use a request similar to the following:
114
129
115
130
```http
116
131
POST https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ApiManagement/service/{serviceName}/gateways/managed/listTrace?api-version=2023-05-01-preview
@@ -120,7 +135,7 @@ Enable tracing by the following steps using calls to the API Management REST API
120
135
121
136
```json
122
137
{
123
-
"traceId": "<trace ID>"
138
+
"traceId": "0123456789abcdef...."
124
139
}
125
140
```
126
141
@@ -134,7 +149,7 @@ For information about customizing trace information, see the [trace](trace-polic
Copy file name to clipboardExpand all lines: articles/api-management/limit-concurrency-policy.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,6 +16,8 @@ ms.author: danlep
16
16
17
17
The `limit-concurrency` policy prevents enclosed policies from executing by more than the specified number of requests at any time. When that number is exceeded, new requests will fail immediately with the `429` Too Many Requests status code.
Copy file name to clipboardExpand all lines: articles/app-service/configure-gateway-required-vnet-integration.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
@@ -35,9 +35,9 @@ You can't use gateway-required virtual network integration:
35
35
36
36
To create a gateway:
37
37
38
-
1.[Create the VPN gateway and subnet](../vpn-gateway/vpn-gateway-howto-point-to-site-resource-manager-portal.md#creategw). Select a route-based VPN type.
38
+
1.[Create the VPN gateway and subnet](../vpn-gateway/point-to-site-certificate-gateway.md#creategw). Select a route-based VPN type.
39
39
40
-
1.[Set the point-to-site addresses](../vpn-gateway/vpn-gateway-howto-point-to-site-resource-manager-portal.md#addresspool). If the gateway isn't in the basic SKU, then IKEV2 must be disabled in the point-to-site configuration and SSTP must be selected. The point-to-site address space must be in the RFC 1918 address blocks 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16.
40
+
1.[Set the point-to-site addresses](../vpn-gateway/point-to-site-certificate-gateway.md#addresspool). If the gateway isn't in the basic SKU, then IKEV2 must be disabled in the point-to-site configuration and SSTP must be selected. The point-to-site address space must be in the RFC 1918 address blocks 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16.
41
41
42
42
If you create the gateway for use with gateway-required virtual network integration, you don't need to upload a certificate. Creating the gateway can take 30 minutes. You won't be able to integrate your app with your virtual network until the gateway is created.
0 commit comments