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/static-web-apps/key-vault-secrets.md
+19-19Lines changed: 19 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,15 +1,15 @@
1
1
---
2
-
title: Securing authentication secrets in Azure Key Vault
3
-
description: Use managed identity to secure authentication secrets in Azure Key Vault.
2
+
title: Secure authentication secrets in Azure Key Vault for Azure Static Web Apps
3
+
description: Use managed identity to secure authentication secrets in Azure Key Vault for Azure Static Web Apps.
4
4
services: static-web-apps
5
5
author: craigshoemaker
6
6
ms.service: static-web-apps
7
7
ms.topic: how-to
8
-
ms.date: 05/17/2021
8
+
ms.date: 06/25/2024
9
9
ms.author: cshoe
10
10
---
11
11
12
-
# Securing authentication secrets in Azure Key Vault
12
+
# Secure authentication secrets in Azure Key Vault for Azure Static Web Apps
13
13
14
14
When configuring custom authentication providers, you may want to store connection secrets in Azure Key Vault. This article demonstrates how to use a managed identity to grant Azure Static Web Apps access to Key Vault for custom authentication secrets.
15
15
@@ -18,7 +18,7 @@ When configuring custom authentication providers, you may want to store connecti
18
18
19
19
Security secrets require the following items to be in place.
20
20
21
-
- Create a system-assigned identity in the Static Web Apps instance.
21
+
- Create a system-assigned identity in your static web app.
22
22
- Grant the identity access to a Key Vault secret.
23
23
- Reference the Key Vault secret from the Static Web Apps application settings.
24
24
@@ -39,9 +39,9 @@ Key Vault integration is not available for:
39
39
40
40
## Create identity
41
41
42
-
1. Open your Static Web Apps site in the Azure portal.
42
+
1. Open your static web apps in the Azure portal.
43
43
44
-
1. Under _Settings_ menu, select **Identity**.
44
+
1. Under _Settings_, select **Identity**.
45
45
46
46
1. Select the **System assigned** tab.
47
47
@@ -69,9 +69,9 @@ You can now add an access policy to allow your static web app to read Key Vault
69
69
70
70
1. Next to the _Select principal_ label, select the **None selected** link.
71
71
72
-
1. In search box, search for your Static Web Apps application name.
72
+
1. In search box, search for your static web app name.
73
73
74
-
1. Select list item that matches your application name.
74
+
1. Select the list item that matches your application name.
75
75
76
76
2. Select **Select**.
77
77
@@ -99,16 +99,16 @@ The access policy is now saved to Key Vault. Next, access the secret's URI to us
99
99
100
100
1. Under the _Settings_ menu, select **Configuration**.
101
101
102
-
2. Under the _Application settings_ section, select **Add**.
102
+
1. Under the _Application settings_ section, select **Add**.
103
103
104
-
3. Enter a name in the text box for the _Name_ field.
104
+
1. Enter a name in the text box for the _Name_ field.
105
105
106
-
4. Determine the secret value in text box for the _Value_ field.
106
+
1. Determine the secret value in text box for the _Value_ field.
107
107
108
108
The secret value is a composite of a few different values. The following template shows how the final string is built.
0 commit comments