Skip to content

Commit 42b7625

Browse files
committed
Updates
1 parent d973b3c commit 42b7625

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

aspnetcore/blazor/security/blazor-web-app-with-entra.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -101,10 +101,10 @@ The callback path (`CallbackPath`) must match the redirect URI (login callback p
101101

102102
Create a client secret in the app's Entra ID registration in the Entra or Azure portal (**Manage** > **Certificates & secrets** > **New client secret**). Use the **Value** of the new secret in the following guidance.
103103

104-
Use one of the following approaches to supply the client secret to the app:
104+
Use either or both of the following approaches to supply the client secret to the app:
105105

106-
* [Secret Manager tool](#secret-manager-tool)
107-
* [Azure Key Vault](#azure-key-vault)
106+
* [Secret Manager tool](#secret-manager-tool): The Secret Manager tool is only used during local development.
107+
* [Azure Key Vault](#azure-key-vault): You can store the client secret in a key vault for use in any environment, including the Development environment locally. Some developers prefer to use key vaults for staging and production deployments and use the [Secret Manager tool](#secret-manager-tool) for local development, which this section explains how to set up.
108108

109109
We strongly recommend that you avoid storing client secrets in project code or configuration files. Use secure authentication flows, such as either of the approaches in this section.
110110

0 commit comments

Comments
 (0)