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/api-management/api-management-howto-mutual-certificates-for-clients.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
@@ -60,7 +60,7 @@ We recommend using key vault certificates because the approach helps improve API
60
60
61
61
### Developer, Basic, Standard, or Premium tier
62
62
63
-
To receive and verify client certificates over HTTP/2 in the Developer, Basic, Standard, or Premium tiers, you must enable the **Negotiate client certificate**.
63
+
To receive and verify client certificates over HTTP/2 in the Developer, Basic, Standard, or Premium tiers, you must enable **Negotiate client certificate**.
64
64
65
65
1. Select **Deployment + infrastructure**, then **Custom domains**.
66
66
1. Select the gateway hostname.
@@ -70,7 +70,7 @@ To receive and verify client certificates over HTTP/2 in the Developer, Basic, S
70
70
71
71
### Consumption, Basic v2, Standard v2, or Premium v2 tier
72
72
73
-
To receive and verify client certificates in the Consumption, Basic v2, Standard v2, or Premium v2 tier, you must enable the **Request client certificate**.
73
+
To receive and verify client certificates in the Consumption, Basic v2, Standard v2, or Premium v2 tier, you must enable **Request client certificate**.
74
74
75
75
1. Select **Deployment + infrastructure**, then **Custom domains**.
76
76
1. Under **Client certificates**, enable **Request client certificate**.
0 commit comments