Skip to content

Commit 8222943

Browse files
committed
Corrected steps.
1 parent d3f3964 commit 8222943

File tree

1 file changed

+11
-10
lines changed

1 file changed

+11
-10
lines changed

articles/active-directory/external-identities/self-service-sign-up-secure-api-connector.md

Lines changed: 11 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,6 @@ Complete the steps in the [Walkthrough: Add an API connector to a sign-up user f
2525

2626
You can protect your API endpoint by using either HTTP basic authentication or HTTPS client certificate authentication. In either case, you provide the credentials that Azure AD uses when calling your API endpoint. Your API endpoint then checks the credentials and performs authorization decisions.
2727

28-
2928
## HTTP basic authentication
3029

3130
HTTP basic authentication is defined in [RFC 2617](https://tools.ietf.org/html/rfc2617). Basic authentication works as follows: Azure AD sends an HTTP request with the client credentials (`username` and `password`) in the `Authorization` header. The credentials are formatted as the base64-encoded string `username:password`. Your API then is responsible for checking these values to perform other authorization decisions.
@@ -34,11 +33,12 @@ To configure an API Connector with HTTP basic authentication, follow these steps
3433

3534
1. Sign in to the [Azure portal](https://portal.azure.com/).
3635
2. Under **Azure services**, select **Azure AD**.
37-
3. Select **API connectors**, and then select the **API Connector** you want to configure.
38-
4. For the **Authentication type**, select **Basic**.
39-
5. Provide the **Username**, and **Password** of your REST API endpoint.
36+
1. In the left menu, select **External Identities**.
37+
1. Select **All API connectors**, and then select the **API Connector** you want to configure.
38+
1. For the **Authentication type**, select **Basic**.
39+
1. Provide the **Username**, and **Password** of your REST API endpoint.
4040
:::image type="content" source="media/secure-api-connector/api-connector-config.png" alt-text="Providing basic authentication configuration for an API connector.":::
41-
6. Select **Save**.
41+
1. Select **Save**.
4242

4343
## HTTPS client certificate authentication
4444

@@ -71,12 +71,13 @@ To configure an API Connector with client certificate authentication, follow the
7171

7272
1. Sign in to the [Azure portal](https://portal.azure.com/).
7373
2. Under **Azure services**, select **Azure AD**.
74-
3. Select **API connectors**, and then select the **API Connector** you want to configure.
75-
4. For the **Authentication type**, select **Certificate**.
76-
5. In the **Upload certificate** box, select your certificate's .pfx file with a private key.
77-
6. In the **Enter Password** box, type the certificate's password.
74+
1. In the left menu, select **External Identities**.
75+
1. Select **All API connectors**, and then select the **API Connector** you want to configure.
76+
1. For the **Authentication type**, select **Certificate**.
77+
1. In the **Upload certificate** box, select your certificate's .pfx file with a private key.
78+
1. In the **Enter Password** box, type the certificate's password.
7879
:::image type="content" source="media/secure-api-connector/api-connector-upload-cert.png" alt-text="Providing certificate authentication configuration for an API connector.":::
79-
7. Select **Save**.
80+
1. Select **Save**.
8081

8182
### Perform authorization decisions
8283
Your API must implement the authorization based on sent client certificates in order to protect the API endpoints. For Azure App Service and Azure Functions, see [configure TLS mutual authentication](../../app-service/app-service-web-configure-tls-mutual-auth.md) to learn how to enable and *validate the certificate from your API code*. You can alternatively use Azure API Management as a layer in front of any API service to [check client certificate properties](

0 commit comments

Comments
 (0)