From 64505d71e59d0452df7b80c1059ffcb98d696d68 Mon Sep 17 00:00:00 2001 From: Tom Dykstra Date: Mon, 7 Oct 2024 15:41:33 -0700 Subject: [PATCH 01/10] address ropc issue --- aspnetcore/fundamentals/use-http-context.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/aspnetcore/fundamentals/use-http-context.md b/aspnetcore/fundamentals/use-http-context.md index e5c63f2fa052..1df8bb4ccf65 100644 --- a/aspnetcore/fundamentals/use-http-context.md +++ b/aspnetcore/fundamentals/use-http-context.md @@ -4,9 +4,11 @@ author: jamesnk description: How to use HttpContext in ASP.NET Core. monikerRange: '>= aspnetcore-3.1' ms.author: wpickett -ms.date: 01/31/2022 +ms.date: 10/07/2024 uid: fundamentals/use-httpcontext --- + + # Use HttpContext in ASP.NET Core [!INCLUDE[](~/includes/not-latest-version.md)] @@ -28,9 +30,11 @@ Commonly used members on `HttpRequest` include: ||A collection of request headers.|`user-agent=Edge`
`x-custom-header=MyValue`| ||A collection of route values. The collection is set when the request is matched to a route.|`language=en`
`article=getstarted`| ||A collection of query values parsed from .|`filter=hello`
`page=1`| -|[HttpRequest.ReadFormAsync()](xref:Microsoft.AspNetCore.Http.HttpRequest.ReadFormAsync(System.Threading.CancellationToken))|A method that reads the request body as a form and returns a form values collection. For information about why `ReadFormAsync` should be used to access form data, see [Prefer ReadFormAsync over Request.Form](xref:fundamentals/best-practices#prefer-readformasync-over-requestform).|`email=user@contoso.com`
`password=TNkt4taM`| +|[HttpRequest.ReadFormAsync()](xref:Microsoft.AspNetCore.Http.HttpRequest.ReadFormAsync(System.Threading.CancellationToken))|A method that reads the request body as a form and returns a form values collection. For information about why `ReadFormAsync` should be used to access form data, see [Prefer ReadFormAsync over Request.Form](xref:fundamentals/best-practices#prefer-readformasync-over-requestform).|`email=user@contoso.com`| ||A for reading the request body.|UTF-8 JSON payload| +[!INCLUDE [managed-identities](~/includes/managed-identities-test-non-production.md)] + ### Get request headers provides access to the request headers sent with the HTTP request. There are two ways to access headers using this collection: From 63ca30c4008797075373354b52c631e5483dbe03 Mon Sep 17 00:00:00 2001 From: Tom Dykstra Date: Tue, 8 Oct 2024 11:41:06 -0700 Subject: [PATCH 02/10] delete unneeded include --- aspnetcore/fundamentals/use-http-context.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/aspnetcore/fundamentals/use-http-context.md b/aspnetcore/fundamentals/use-http-context.md index 1df8bb4ccf65..05266eb35304 100644 --- a/aspnetcore/fundamentals/use-http-context.md +++ b/aspnetcore/fundamentals/use-http-context.md @@ -33,8 +33,6 @@ Commonly used members on `HttpRequest` include: |[HttpRequest.ReadFormAsync()](xref:Microsoft.AspNetCore.Http.HttpRequest.ReadFormAsync(System.Threading.CancellationToken))|A method that reads the request body as a form and returns a form values collection. For information about why `ReadFormAsync` should be used to access form data, see [Prefer ReadFormAsync over Request.Form](xref:fundamentals/best-practices#prefer-readformasync-over-requestform).|`email=user@contoso.com`| ||A for reading the request body.|UTF-8 JSON payload| -[!INCLUDE [managed-identities](~/includes/managed-identities-test-non-production.md)] - ### Get request headers provides access to the request headers sent with the HTTP request. There are two ways to access headers using this collection: From 294b9d5c718b3f30cbfeec8751878f5bc3a308ee Mon Sep 17 00:00:00 2001 From: Tom Dykstra Date: Wed, 16 Oct 2024 15:32:54 -0700 Subject: [PATCH 03/10] ropc changes --- aspnetcore/fundamentals/configuration/index.md | 8 ++++++-- .../fundamentals/configuration/index/includes/index3-5.md | 2 ++ .../fundamentals/configuration/index/includes/index6.md | 5 +++++ .../fundamentals/configuration/index/includes/index7.md | 5 +++++ aspnetcore/fundamentals/configuration/options.md | 3 ++- aspnetcore/includes/managed-identities-conn-string.md | 8 ++++++++ 6 files changed, 28 insertions(+), 3 deletions(-) create mode 100644 aspnetcore/includes/managed-identities-conn-string.md diff --git a/aspnetcore/fundamentals/configuration/index.md b/aspnetcore/fundamentals/configuration/index.md index 785f46db77a5..3d7350c816c2 100644 --- a/aspnetcore/fundamentals/configuration/index.md +++ b/aspnetcore/fundamentals/configuration/index.md @@ -158,6 +158,7 @@ Configuration data guidelines: * Never store passwords or other sensitive data in configuration provider code or in plain text configuration files. The [Secret Manager](xref:security/app-secrets) tool can be used to store secrets in development. * Don't use production secrets in development or test environments. * Specify secrets outside of the project so that they can't be accidentally committed to a source code repository. +* Avoid the use of passwords in production apps; for more information, see [Secure authentication flows](xref:security/index#secure-authentication-flows). By [default](#default), the user secrets configuration source is registered after the JSON configuration sources. Therefore, user secrets keys take precedence over keys in `appsettings.json` and `appsettings.{Environment}.json`. @@ -165,8 +166,7 @@ For more information on storing passwords or other sensitive data: * * : Includes advice on using environment variables to store sensitive data. The Secret Manager tool uses the [File configuration provider](#fcp) to store user secrets in a JSON file on the local system. - -[Azure Key Vault](https://azure.microsoft.com/services/key-vault/) safely stores app secrets for ASP.NET Core apps. For more information, see . +* [Azure Key Vault](https://azure.microsoft.com/services/key-vault/) safely stores app secrets for ASP.NET Core apps. For more information, see . @@ -408,6 +408,8 @@ The preferred way to read hierarchical configuration data is using the options p ## Configuration keys and values +[!INCLUDE [managed-identities](~/includes/managed-identities-conn-strings.md)] + Configuration keys: * Are case-insensitive. For example, `ConnectionString` and `connectionstring` are treated as equivalent keys. @@ -459,6 +461,8 @@ The preceding sequence of providers is used in the [default configuration](#defa ### Connection string prefixes +[!INCLUDE [managed-identities](~/includes/managed-identities-conn-strings.md)] + The Configuration API has special processing rules for four connection string environment variables. These connection strings are involved in configuring Azure connection strings for the app environment. Environment variables with the prefixes shown in the table are loaded into the app with the [default configuration](#default) or when no prefix is supplied to `AddEnvironmentVariables`. | Connection string prefix | Provider | diff --git a/aspnetcore/fundamentals/configuration/index/includes/index3-5.md b/aspnetcore/fundamentals/configuration/index/includes/index3-5.md index afb6669b5f05..bc62dc09c444 100644 --- a/aspnetcore/fundamentals/configuration/index/includes/index3-5.md +++ b/aspnetcore/fundamentals/configuration/index/includes/index3-5.md @@ -149,6 +149,8 @@ Custom configuration providers aren't required to implement array binding. ## Custom configuration provider +[!INCLUDE [managed-identities](~/includes/managed-identities-conn-strings.md)] + The sample app demonstrates how to create a basic configuration provider that reads configuration key-value pairs from a database using [Entity Framework (EF)](/ef/core/). The provider has the following characteristics: diff --git a/aspnetcore/fundamentals/configuration/index/includes/index6.md b/aspnetcore/fundamentals/configuration/index/includes/index6.md index 906ebb7913d5..e23683ea1012 100644 --- a/aspnetcore/fundamentals/configuration/index/includes/index6.md +++ b/aspnetcore/fundamentals/configuration/index/includes/index6.md @@ -135,6 +135,7 @@ Configuration data guidelines: * Never store passwords or other sensitive data in configuration provider code or in plain text configuration files. The [Secret Manager](xref:security/app-secrets) tool can be used to store secrets in development. * Don't use production secrets in development or test environments. * Specify secrets outside of the project so that they can't be accidentally committed to a source code repository. +* Avoid the use of passwords in production apps; for more information, see [Secure authentication flows](xref:security/index#secure-authentication-flows). By [default](#default), the user secrets configuration source is registered after the JSON configuration sources. Therefore, user secrets keys take precedence over keys in `appsettings.json` and `appsettings.{Environment}.json`. @@ -385,6 +386,8 @@ The preferred way to read hierarchical configuration data is using the options p ## Configuration keys and values +[!INCLUDE [managed-identities](~/includes/managed-identities-conn-strings.md)] + Configuration keys: * Are case-insensitive. For example, `ConnectionString` and `connectionstring` are treated as equivalent keys. @@ -436,6 +439,8 @@ The preceding sequence of providers is used in the [default configuration](#defa ### Connection string prefixes +[!INCLUDE [managed-identities](~/includes/managed-identities-conn-strings.md)] + The Configuration API has special processing rules for four connection string environment variables. These connection strings are involved in configuring Azure connection strings for the app environment. Environment variables with the prefixes shown in the table are loaded into the app with the [default configuration](#default) or when no prefix is supplied to `AddEnvironmentVariables`. | Connection string prefix | Provider | diff --git a/aspnetcore/fundamentals/configuration/index/includes/index7.md b/aspnetcore/fundamentals/configuration/index/includes/index7.md index 76fce7e30b64..3fcad1e10426 100644 --- a/aspnetcore/fundamentals/configuration/index/includes/index7.md +++ b/aspnetcore/fundamentals/configuration/index/includes/index7.md @@ -140,6 +140,7 @@ Configuration data guidelines: * Never store passwords or other sensitive data in configuration provider code or in plain text configuration files. The [Secret Manager](xref:security/app-secrets) tool can be used to store secrets in development. * Don't use production secrets in development or test environments. * Specify secrets outside of the project so that they can't be accidentally committed to a source code repository. +* Avoid the use of passwords in production apps; for more information, see [Secure authentication flows](xref:security/index#secure-authentication-flows). By [default](#default), the user secrets configuration source is registered after the JSON configuration sources. Therefore, user secrets keys take precedence over keys in `appsettings.json` and `appsettings.{Environment}.json`. @@ -390,6 +391,8 @@ The preferred way to read hierarchical configuration data is using the options p ## Configuration keys and values +[!INCLUDE [managed-identities](~/includes/managed-identities-conn-strings.md)] + Configuration keys: * Are case-insensitive. For example, `ConnectionString` and `connectionstring` are treated as equivalent keys. @@ -441,6 +444,8 @@ The preceding sequence of providers is used in the [default configuration](#defa ### Connection string prefixes +[!INCLUDE [managed-identities](~/includes/managed-identities-conn-strings.md)] + The Configuration API has special processing rules for four connection string environment variables. These connection strings are involved in configuring Azure connection strings for the app environment. Environment variables with the prefixes shown in the table are loaded into the app with the [default configuration](#default) or when no prefix is supplied to `AddEnvironmentVariables`. | Connection string prefix | Provider | diff --git a/aspnetcore/fundamentals/configuration/options.md b/aspnetcore/fundamentals/configuration/options.md index 373e594d3da4..7e05404883c1 100644 --- a/aspnetcore/fundamentals/configuration/options.md +++ b/aspnetcore/fundamentals/configuration/options.md @@ -17,7 +17,8 @@ when updating this article --> :::moniker range=">= aspnetcore-7.0" -By [Rick Anderson](https://twitter.com/RickAndMSFT). +By [Rick Anderson](https://twitter.com/RickAndMSFT) + The options pattern uses classes to provide strongly typed access to groups of related settings. When [configuration settings](xref:fundamentals/configuration/index) are isolated by scenario into separate classes, the app adheres to two important software engineering principles: diff --git a/aspnetcore/includes/managed-identities-conn-string.md b/aspnetcore/includes/managed-identities-conn-string.md new file mode 100644 index 000000000000..1a5fac47e7c4 --- /dev/null +++ b/aspnetcore/includes/managed-identities-conn-string.md @@ -0,0 +1,8 @@ +--- +author: tdykstra +ms.author: tdykstra +ms.date: 10/16/2024 +ms.topic: include +--- +> [!WARNING] +> This article shows the use of connection strings. With a local database the user doesn't have to be authenticated, but in production, connection strings sometimes include a password to authenticate. A resource owner password credential (ROPC) is a security risk that should be avoided in production databases. Production apps should use the most secure authentication flow available. For more information on authentication for apps deployed to test or production non-local environments, see [Secure authentication flows](xref:security/index#secure-authentication-flows). From e43b2ceaf590d71beda99517f0da1d489074286f Mon Sep 17 00:00:00 2001 From: Tom Dykstra Date: Wed, 16 Oct 2024 16:24:51 -0700 Subject: [PATCH 04/10] rename string to strings --- ...entities-conn-string.md => managed-identities-conn-strings.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename aspnetcore/includes/{managed-identities-conn-string.md => managed-identities-conn-strings.md} (100%) diff --git a/aspnetcore/includes/managed-identities-conn-string.md b/aspnetcore/includes/managed-identities-conn-strings.md similarity index 100% rename from aspnetcore/includes/managed-identities-conn-string.md rename to aspnetcore/includes/managed-identities-conn-strings.md From 6a2ddcfbffb3db52043eed774fa35acaf7d8e4df Mon Sep 17 00:00:00 2001 From: Tom Dykstra Date: Wed, 16 Oct 2024 16:32:10 -0700 Subject: [PATCH 05/10] markdownlint --- aspnetcore/fundamentals/configuration/options.md | 1 - 1 file changed, 1 deletion(-) diff --git a/aspnetcore/fundamentals/configuration/options.md b/aspnetcore/fundamentals/configuration/options.md index 7e05404883c1..4c0ab6a01228 100644 --- a/aspnetcore/fundamentals/configuration/options.md +++ b/aspnetcore/fundamentals/configuration/options.md @@ -19,7 +19,6 @@ when updating this article --> By [Rick Anderson](https://twitter.com/RickAndMSFT) - The options pattern uses classes to provide strongly typed access to groups of related settings. When [configuration settings](xref:fundamentals/configuration/index) are isolated by scenario into separate classes, the app adheres to two important software engineering principles: * [Encapsulation](/dotnet/standard/modern-web-apps-azure-architecture/architectural-principles#encapsulation): From a363bd6d18c431ea0b52dac288b08109fb11815f Mon Sep 17 00:00:00 2001 From: Tom Dykstra Date: Wed, 16 Oct 2024 16:38:42 -0700 Subject: [PATCH 06/10] delete unneeded word --- aspnetcore/includes/managed-identities-conn-strings.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnetcore/includes/managed-identities-conn-strings.md b/aspnetcore/includes/managed-identities-conn-strings.md index 1a5fac47e7c4..47f14d30d7aa 100644 --- a/aspnetcore/includes/managed-identities-conn-strings.md +++ b/aspnetcore/includes/managed-identities-conn-strings.md @@ -5,4 +5,4 @@ ms.date: 10/16/2024 ms.topic: include --- > [!WARNING] -> This article shows the use of connection strings. With a local database the user doesn't have to be authenticated, but in production, connection strings sometimes include a password to authenticate. A resource owner password credential (ROPC) is a security risk that should be avoided in production databases. Production apps should use the most secure authentication flow available. For more information on authentication for apps deployed to test or production non-local environments, see [Secure authentication flows](xref:security/index#secure-authentication-flows). +> This article shows the use of connection strings. With a local database the user doesn't have to be authenticated, but in production, connection strings sometimes include a password to authenticate. A resource owner password credential (ROPC) is a security risk that should be avoided in production databases. Production apps should use the most secure authentication flow available. For more information on authentication for apps deployed to test or production environments, see [Secure authentication flows](xref:security/index#secure-authentication-flows). From f1bf60d67d7f7d2590f791861e00e5e247e6ec83 Mon Sep 17 00:00:00 2001 From: Tom Dykstra Date: Wed, 16 Oct 2024 18:48:26 -0700 Subject: [PATCH 07/10] mark ropc done --- aspnetcore/fundamentals/configuration/index.md | 1 + .../fundamentals/configuration/index/includes/index3-5.md | 2 +- aspnetcore/fundamentals/configuration/index/includes/index6.md | 2 +- aspnetcore/fundamentals/configuration/index/includes/index7.md | 2 +- aspnetcore/includes/managed-identities-conn-strings.md | 1 + 5 files changed, 5 insertions(+), 3 deletions(-) diff --git a/aspnetcore/fundamentals/configuration/index.md b/aspnetcore/fundamentals/configuration/index.md index 3d7350c816c2..33ac26d8f0f0 100644 --- a/aspnetcore/fundamentals/configuration/index.md +++ b/aspnetcore/fundamentals/configuration/index.md @@ -8,6 +8,7 @@ ms.custom: mvc ms.date: 04/26/2024 uid: fundamentals/configuration/index --- + # Configuration in ASP.NET Core By [Rick Anderson](https://twitter.com/RickAndMSFT) and [Kirk Larkin](https://twitter.com/serpent5) diff --git a/aspnetcore/fundamentals/configuration/index/includes/index3-5.md b/aspnetcore/fundamentals/configuration/index/includes/index3-5.md index bc62dc09c444..bbc9ac35ebe2 100644 --- a/aspnetcore/fundamentals/configuration/index/includes/index3-5.md +++ b/aspnetcore/fundamentals/configuration/index/includes/index3-5.md @@ -1,5 +1,5 @@ :::moniker range=">= aspnetcore-5.0 < aspnetcore-6.0" - + ## Kestrel endpoint configuration diff --git a/aspnetcore/fundamentals/configuration/index/includes/index6.md b/aspnetcore/fundamentals/configuration/index/includes/index6.md index e23683ea1012..10aa21d018f4 100644 --- a/aspnetcore/fundamentals/configuration/index/includes/index6.md +++ b/aspnetcore/fundamentals/configuration/index/includes/index6.md @@ -1,5 +1,5 @@ :::moniker range="= aspnetcore-6.0" - + Application configuration in ASP.NET Core is performed using one or more [configuration providers](#cp). Configuration providers read configuration data from key-value pairs using a variety of configuration sources: * Settings files, such as `appsettings.json` diff --git a/aspnetcore/fundamentals/configuration/index/includes/index7.md b/aspnetcore/fundamentals/configuration/index/includes/index7.md index 3fcad1e10426..3c54b4d864c1 100644 --- a/aspnetcore/fundamentals/configuration/index/includes/index7.md +++ b/aspnetcore/fundamentals/configuration/index/includes/index7.md @@ -1,5 +1,5 @@ :::moniker range="= aspnetcore-7.0" - + Application configuration in ASP.NET Core is performed using one or more [configuration providers](#cp). Configuration providers read configuration data from key-value pairs using a variety of configuration sources: * Settings files, such as `appsettings.json` diff --git a/aspnetcore/includes/managed-identities-conn-strings.md b/aspnetcore/includes/managed-identities-conn-strings.md index 47f14d30d7aa..e8d80e875779 100644 --- a/aspnetcore/includes/managed-identities-conn-strings.md +++ b/aspnetcore/includes/managed-identities-conn-strings.md @@ -4,5 +4,6 @@ ms.author: tdykstra ms.date: 10/16/2024 ms.topic: include --- + > [!WARNING] > This article shows the use of connection strings. With a local database the user doesn't have to be authenticated, but in production, connection strings sometimes include a password to authenticate. A resource owner password credential (ROPC) is a security risk that should be avoided in production databases. Production apps should use the most secure authentication flow available. For more information on authentication for apps deployed to test or production environments, see [Secure authentication flows](xref:security/index#secure-authentication-flows). From a2d530088acbfe66aa798ce06eb582cee2d4e781 Mon Sep 17 00:00:00 2001 From: Tom Dykstra Date: Thu, 17 Oct 2024 11:20:25 -0700 Subject: [PATCH 08/10] Update aspnetcore/fundamentals/configuration/options.md --- aspnetcore/fundamentals/configuration/options.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnetcore/fundamentals/configuration/options.md b/aspnetcore/fundamentals/configuration/options.md index 4c0ab6a01228..373e594d3da4 100644 --- a/aspnetcore/fundamentals/configuration/options.md +++ b/aspnetcore/fundamentals/configuration/options.md @@ -17,7 +17,7 @@ when updating this article --> :::moniker range=">= aspnetcore-7.0" -By [Rick Anderson](https://twitter.com/RickAndMSFT) +By [Rick Anderson](https://twitter.com/RickAndMSFT). The options pattern uses classes to provide strongly typed access to groups of related settings. When [configuration settings](xref:fundamentals/configuration/index) are isolated by scenario into separate classes, the app adheres to two important software engineering principles: From 28c27e1c6759ce2d89e9acd6f0ad53f7a83cc6fd Mon Sep 17 00:00:00 2001 From: Rick Anderson <3605364+Rick-Anderson@users.noreply.github.com> Date: Mon, 28 Oct 2024 16:56:54 -0600 Subject: [PATCH 09/10] Update aspnetcore/fundamentals/configuration/index.md Co-authored-by: Tom Dykstra <1569635+tdykstra@users.noreply.github.com> --- aspnetcore/fundamentals/configuration/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnetcore/fundamentals/configuration/index.md b/aspnetcore/fundamentals/configuration/index.md index 33ac26d8f0f0..bd771b4957cf 100644 --- a/aspnetcore/fundamentals/configuration/index.md +++ b/aspnetcore/fundamentals/configuration/index.md @@ -159,7 +159,7 @@ Configuration data guidelines: * Never store passwords or other sensitive data in configuration provider code or in plain text configuration files. The [Secret Manager](xref:security/app-secrets) tool can be used to store secrets in development. * Don't use production secrets in development or test environments. * Specify secrets outside of the project so that they can't be accidentally committed to a source code repository. -* Avoid the use of passwords in production apps; for more information, see [Secure authentication flows](xref:security/index#secure-authentication-flows). +* Production apps should use the most secure authentication flow available. For more information, see [Secure authentication flows](xref:security/index#secure-authentication-flows). By [default](#default), the user secrets configuration source is registered after the JSON configuration sources. Therefore, user secrets keys take precedence over keys in `appsettings.json` and `appsettings.{Environment}.json`. From a808c1b166e481c3555cd828d96c721d36a3d0db Mon Sep 17 00:00:00 2001 From: Tom Dykstra <1569635+tdykstra@users.noreply.github.com> Date: Mon, 28 Oct 2024 17:24:00 -0700 Subject: [PATCH 10/10] Apply suggestions from code review --- aspnetcore/fundamentals/configuration/index/includes/index6.md | 2 +- aspnetcore/fundamentals/configuration/index/includes/index7.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/aspnetcore/fundamentals/configuration/index/includes/index6.md b/aspnetcore/fundamentals/configuration/index/includes/index6.md index 10aa21d018f4..469a6a10039f 100644 --- a/aspnetcore/fundamentals/configuration/index/includes/index6.md +++ b/aspnetcore/fundamentals/configuration/index/includes/index6.md @@ -135,7 +135,7 @@ Configuration data guidelines: * Never store passwords or other sensitive data in configuration provider code or in plain text configuration files. The [Secret Manager](xref:security/app-secrets) tool can be used to store secrets in development. * Don't use production secrets in development or test environments. * Specify secrets outside of the project so that they can't be accidentally committed to a source code repository. -* Avoid the use of passwords in production apps; for more information, see [Secure authentication flows](xref:security/index#secure-authentication-flows). +* Production apps should use the most secure authentication flow available. For more information, see [Secure authentication flows](xref:security/index#secure-authentication-flows). By [default](#default), the user secrets configuration source is registered after the JSON configuration sources. Therefore, user secrets keys take precedence over keys in `appsettings.json` and `appsettings.{Environment}.json`. diff --git a/aspnetcore/fundamentals/configuration/index/includes/index7.md b/aspnetcore/fundamentals/configuration/index/includes/index7.md index 3c54b4d864c1..189d7f998989 100644 --- a/aspnetcore/fundamentals/configuration/index/includes/index7.md +++ b/aspnetcore/fundamentals/configuration/index/includes/index7.md @@ -140,7 +140,7 @@ Configuration data guidelines: * Never store passwords or other sensitive data in configuration provider code or in plain text configuration files. The [Secret Manager](xref:security/app-secrets) tool can be used to store secrets in development. * Don't use production secrets in development or test environments. * Specify secrets outside of the project so that they can't be accidentally committed to a source code repository. -* Avoid the use of passwords in production apps; for more information, see [Secure authentication flows](xref:security/index#secure-authentication-flows). +* Production apps should use the most secure authentication flow available. For more information, see [Secure authentication flows](xref:security/index#secure-authentication-flows). By [default](#default), the user secrets configuration source is registered after the JSON configuration sources. Therefore, user secrets keys take precedence over keys in `appsettings.json` and `appsettings.{Environment}.json`.