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.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,14 +28,14 @@ For information about managing certificates using the API Management REST API, s
28
28
29
29
This guide shows you how to configure your API Management service instance to use client certificate authentication to access the back-end service for an API. Before following the steps in this article, you should have your back-end service configured for client certificate authentication ([to configure certificate authentication in Azure WebSites refer to this article][to configure certificate authentication in Azure WebSites refer to this article]). You need access to the certificate and the password for uploading it to the API Management service.
30
30
31
-
## <aname="step1"> </a>Upload a client certificate
Follow the steps below to upload a new client certificate. If you have not created an API Management service instance yet, see the tutorial [Create an API Management service instance][Create an API Management service instance].
36
36
37
37
1. Navigate to your Azure API Management service instance in the Azure portal.
4. Browse for the certificate, provide its ID and password.
@@ -44,7 +44,7 @@ Follow the steps below to upload a new client certificate. If you have not creat
44
44
> [!NOTE]
45
45
> The certificate must be in **.pfx** format. Self-signed certificates are allowed.
46
46
47
-
Once the certificate is uploaded, it shows in the **Client certificates**. If you have many certificates, make a note of the thumbprint of the desired certificate in order to [Configure an API to use a client certificate for gateway authentication][Configure an API to use a client certificate for gateway authentication].
47
+
Once the certificate is uploaded, it shows in the **Certificates**. If you have many certificates, make a note of the thumbprint of the desired certificate in order to [Configure an API to use a client certificate for gateway authentication][Configure an API to use a client certificate for gateway authentication].
48
48
49
49
> [!NOTE]
50
50
> To turn off certificate chain validation when using, for example, a self-signed certificate, follow the steps described in this FAQ [item](api-management-faq.md#can-i-use-a-self-signed-ssl-certificate-for-a-back-end).
@@ -53,7 +53,7 @@ Once the certificate is uploaded, it shows in the **Client certificates**. If y
53
53
54
54
To delete a certificate, click context menu **...** and select **Delete** beside the certificate.
If the certificate is in use by an API, then a warning screen is displayed. To delete the certificate, you must first remove the certificate from any APIs that are configured to use it.
Copy file name to clipboardExpand all lines: articles/azure-resource-manager/move-limitations/app-service-move-limitations.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
@@ -18,7 +18,7 @@ When moving a Web App across subscriptions, the following guidance applies:
18
18
- App Service plans
19
19
- Uploaded or imported SSL certificates
20
20
- App Service Environments
21
-
- All App Service resources in the resource group must be moved together.
21
+
- All App Service resources in the resource group must be moved together. Note that App Service Environments cannot be moved to a new Resource Group nor to a new Subscription.
22
22
- You can move a certificate bound to a web without deleting the SSL bindings, as long as the certificate is moved with all other resources in the resource group.
23
23
- App Service resources can only be moved from the resource group in which they were originally created. If an App Service resource is no longer in its original resource group, move it back to its original resource group. Then, move the resource across subscriptions.
0 commit comments