Skip to content

Commit b30d985

Browse files
committed
improvements to grammar
1 parent 735297c commit b30d985

File tree

1 file changed

+23
-26
lines changed

1 file changed

+23
-26
lines changed

articles/azure-maps/how-to-secure-webapp-users.md

Lines changed: 23 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
2-
title: How to secure a web application with interactive single-sign-in
2+
title: How to secure a web application with interactive single sign-in
33
titleSuffix: Azure Maps
4-
description: How to configure a web application which supports Azure AD single-sign-on with Azure Maps Web SDK using OpenID Connect protocol.
4+
description: How to configure a web application that supports Azure AD single sign-in with Azure Maps Web SDK using OpenID Connect protocol.
55
author: eriklindeman
66
ms.author: eriklind
77
ms.date: 06/12/2020
@@ -13,49 +13,46 @@ ms.custom: devx-track-js
1313

1414
# Secure a web application with user sign-in
1515

16-
The following guide pertains to an application which is hosted on web servers, maintains multiple business scenarios, and deploys to web servers. The application has the requirement to provide protected resources secured only to Azure AD users. The objective of the scenario is to enable the web application to authenticate to Azure AD and call Azure Maps REST APIs on behalf of the user.
16+
The following guide pertains to an application that is hosted on web servers, maintains multiple business scenarios, and deploys to web servers. The application has the requirement to provide protected resources secured only to Azure AD users. The objective of the scenario is to enable the web application to authenticate to Azure AD and call Azure Maps REST APIs on behalf of the user.
1717

1818
[!INCLUDE [authentication details](./includes/view-authentication-details.md)]
1919

2020
## Create an application registration in Azure AD
2121

22-
You must create the web application in Azure AD for users to sign in. This web application will then delegate user access to Azure Maps REST APIs.
22+
You must create the web application in Azure AD for users to sign in. This web application then delegates user access to Azure Maps REST APIs.
2323

2424
1. In the Azure portal, in the list of Azure services, select **Azure Active Directory** > **App registrations** > **New registration**.
2525

26-
> [!div class="mx-imgBorder"]
27-
> ![App registration](./media/how-to-manage-authentication/app-registration.png)
26+
:::image type="content" source="./media/how-to-manage-authentication/app-registration.png" alt-text="A screenshot showing App registration." lightbox="./media/how-to-manage-authentication/app-registration.png":::
2827

29-
2. Enter a **Name**, choose a **Support account type**, provide a redirect URI which will represent the url which Azure AD will issue the token and is the url where the map control is hosted. For more details please see Azure AD [Scenario: Web app that signs in users](../active-directory/develop/scenario-web-app-sign-user-overview.md). Complete the provided steps from the Azure AD scenario.
28+
2. Enter a **Name**, choose a **Support account type**, provide a redirect URI that represents the url to which Azure AD issues the token, which is the url where the map control is hosted. For more information, see Azure AD [Scenario: Web app that signs in users](../active-directory/develop/scenario-web-app-sign-user-overview.md). Complete the provided steps from the Azure AD scenario.
3029

31-
3. Once the application registration is complete, Confirm that application sign-in works for users. Once sign-in works, then the application can be granted delegated access to Azure Maps REST APIs.
32-
33-
4. To assign delegated API permissions to Azure Maps, go to the application. Then select **API permissions** > **Add a permission**. Under **APIs my organization uses**, search for and select **Azure Maps**.
30+
3. Once the application registration is complete, confirm that application sign-in works for users. Once sign-in works, the application can be granted delegated access to Azure Maps REST APIs.
3431

35-
> [!div class="mx-imgBorder"]
36-
> ![Add app API permissions](./media/how-to-manage-authentication/app-permissions.png)
32+
4. To assign delegated API permissions to Azure Maps, go to the application and select **API permissions** > **Add a permission**. select **Azure Maps** in the **APIs my organization uses** list.
33+
34+
:::image type="content" source="./media/how-to-manage-authentication/app-permissions.png" alt-text="A screenshot showing add app API permissions." lightbox="./media/how-to-manage-authentication/app-permissions.png":::
3735

3836
5. Select the check box next to **Access Azure Maps**, and then select **Add permissions**.
3937

40-
> [!div class="mx-imgBorder"]
41-
> ![Select app API permissions](./media/how-to-manage-authentication/select-app-permissions.png)
38+
:::image type="content" source="./media/how-to-manage-authentication/select-app-permissions.png" alt-text="A screenshot showing select app API permissions." lightbox="./media/how-to-manage-authentication/select-app-permissions.png":::
39+
40+
6. Enable the web application to call Azure Maps REST APIs by configuring the app registration with an application secret, For detailed steps, see [A web app that calls web APIs: App registration](../active-directory/develop/scenario-web-app-call-api-app-registration.md). A secret is required to authenticate to Azure AD on-behalf of the user. The app registration certificate or secret should be stored in a secure store for the web application to retrieve to authenticate to Azure AD.
41+
42+
* This step may be skipped if the application already has an Azure AD app registration and secret configured.
43+
44+
> [!TIP]
45+
> If the application is hosted in an Azure environment, we recommend using [Managed identities for Azure resources](../active-directory/managed-identities-azure-resources/overview.md) and an Azure Key Vault instance to access secrets by [acquiring an access token](../active-directory/managed-identities-azure-resources/how-to-use-vm-token.md) for accessing Azure Key Vault secrets or certificates. To connect to Azure Key Vault to retrieve secrets, see [tutorial to connect through managed identity](../key-vault/general/tutorial-net-create-vault-azure-web-app.md).
4246
43-
6. Enable the web application to call Azure Maps REST APIs by configuring the app registration with an application secret, For detailed steps, see [A web app that calls web APIs: App registration](../active-directory/develop/scenario-web-app-call-api-app-registration.md). A secret is required to authenticate to Azure AD on-behalf of the user. The app registration certificate or secret should be stored in a secure store for the web application to retrieve to authenticate to Azure AD.
44-
45-
* If the application already has configured an Azure AD app registration and a secret this step may be skipped.
47+
7. Implement a secure token endpoint for the Azure Maps Web SDK to access a token.
4648

47-
> [!Tip]
48-
> If the application is hosted in an Azure environment, we recommend using [Managed identities for Azure resources](../active-directory/managed-identities-azure-resources/overview.md) and an Azure Key Vault instance to access secrets by [acquiring an access token](../active-directory/managed-identities-azure-resources/how-to-use-vm-token.md) for accessing Azure Key Vault secrets or certificates. To connect to Azure Key Vault to retrieve secrets, see [tutorial to connect through managed identity](../key-vault/general/tutorial-net-create-vault-azure-web-app.md).
49-
50-
7. Implement a secure token endpoint for the Azure Maps Web SDK to access a token.
51-
52-
* For a sample token controller, see [Azure Maps Azure AD Samples](https://github.com/Azure-Samples/Azure-Maps-AzureAD-Samples/blob/master/src/OpenIdConnect/AzureMapsOpenIdConnectv1/AzureMapsOpenIdConnect/Controllers/TokenController.cs).
49+
* For a sample token controller, see [Azure Maps Azure AD Samples](https://github.com/Azure-Samples/Azure-Maps-AzureAD-Samples/blob/master/src/OpenIdConnect/AzureMapsOpenIdConnectv1/AzureMapsOpenIdConnect/Controllers/TokenController.cs).
5350
* For a non-AspNetCore implementation or other, see [Acquire token for the app](../active-directory/develop/scenario-web-app-call-api-acquire-token.md) from Azure AD documentation.
5451
* The secured token endpoint is responsible to return an access token for the authenticated and authorized user to call Azure Maps REST APIs.
5552

56-
8. Configure Azure role-based access control (Azure RBAC) for users or groups. See [grant role-based access for users](#grant-role-based-access-for-users-to-azure-maps).
53+
8. To configure Azure role-based access control (Azure RBAC) for users or groups, see [grant role-based access for users](#grant-role-based-access-for-users-to-azure-maps).
5754

58-
9. Configure the web application page with the Azure Maps Web SDK to access the secure token endpoint.
55+
9. Configure the web application page with the Azure Maps Web SDK to access the secure token endpoint.
5956

6057
```javascript
6158
var map = new atlas.Map("map", {
@@ -102,4 +99,4 @@ Find the API usage metrics for your Azure Maps account:
10299
103100
Explore samples that show how to integrate Azure AD with Azure Maps:
104101
> [!div class="nextstepaction"]
105-
> [Azure Maps Azure AD Web App Samples](https://github.com/Azure-Samples/Azure-Maps-AzureAD-Samples/tree/master/src/OpenIdConnect)
102+
> [Azure Maps Azure AD Web App Samples](https://github.com/Azure-Samples/Azure-Maps-AzureAD-Samples/tree/master/src/OpenIdConnect)

0 commit comments

Comments
 (0)