From 9729bc8889267fb662f16cf86c9b8192109e0978 Mon Sep 17 00:00:00 2001 From: Mihir Karandikar Date: Mon, 30 Oct 2017 19:35:38 +0530 Subject: [PATCH 1/6] Fix typo in configuration.md (#4656) "a" -> "an" --- aspnetcore/fundamentals/configuration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnetcore/fundamentals/configuration.md b/aspnetcore/fundamentals/configuration.md index 9843b3060d..7b33e7ea38 100644 --- a/aspnetcore/fundamentals/configuration.md +++ b/aspnetcore/fundamentals/configuration.md @@ -46,7 +46,7 @@ Configuration consists of a hierarchical list of name-value pairs in which the n Console.WriteLine($"option1 = {Configuration["subsection:suboption1"]}"); ``` -To work with arrays in JSON-formatted configuration sources, use a array index as part of the colon-separated string. The following example gets the name of the first item in the preceding `wizards` array: +To work with arrays in JSON-formatted configuration sources, use an array index as part of the colon-separated string. The following example gets the name of the first item in the preceding `wizards` array: ```csharp Console.Write($"{Configuration["wizards:0:Name"]}, "); From aa039cc01b055fcbe22616785c2df3569031e5cb Mon Sep 17 00:00:00 2001 From: Michael DePouw Date: Mon, 30 Oct 2017 11:07:31 -0400 Subject: [PATCH 2/6] fix bad anchor link (#4660) reference: https://opbuildstorageprod.blob.core.windows.net/report/2017%5C10%5C13%5C6a0d29ae-bb37-09f1-c55a-4cfa862c6784%5CPullRequest%5C201710131248087361-4562%5Cworkflow_report.html?sv=2015-02-21&sr=b&sig=GbG0qgcJNtJMXYbbzHZqcp2BJNdAKtUYmbwoSscw5IY%3D&st=2017-10-13T12%3A50%3A41Z&se=2017-11-13T12%3A55%3A41Z&sp=r --- aspnetcore/security/authorization/claims.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnetcore/security/authorization/claims.md b/aspnetcore/security/authorization/claims.md index 4b15faa5e8..9995997637 100644 --- a/aspnetcore/security/authorization/claims.md +++ b/aspnetcore/security/authorization/claims.md @@ -119,4 +119,4 @@ public class SalaryController : Controller In the above example any identity which fulfills the `EmployeeOnly` policy can access the `Payslip` action as that policy is enforced on the controller. However in order to call the `UpdateSalary` action the identity must fulfill *both* the `EmployeeOnly` policy and the `HumanResources` policy. -If you want more complicated policies, such as taking a date of birth claim, calculating an age from it then checking the age is 21 or older then you need to write [custom policy handlers](policies.md#security-authorization-policies-based). +If you want more complicated policies, such as taking a date of birth claim, calculating an age from it then checking the age is 21 or older then you need to write [custom policy handlers](policies.md). From 619c44889cbce61996906c6c8f880da1bbb504eb Mon Sep 17 00:00:00 2001 From: Michael DePouw Date: Mon, 30 Oct 2017 11:09:59 -0400 Subject: [PATCH 3/6] fix bad anchor link (#4661) reference: https://github.com/aspnet/Docs/issues/4649 --- aspnetcore/security/authorization/limitingidentitybyscheme.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnetcore/security/authorization/limitingidentitybyscheme.md b/aspnetcore/security/authorization/limitingidentitybyscheme.md index 91140f2c07..c8abd3a02f 100644 --- a/aspnetcore/security/authorization/limitingidentitybyscheme.md +++ b/aspnetcore/security/authorization/limitingidentitybyscheme.md @@ -131,7 +131,7 @@ In the preceding code, only the handler with the "Bearer" scheme runs. Any cooki ## Selecting the scheme with policies -If you prefer to specify the desired schemes in [policy](xref:security/authorization/policies#security-authorization-policies-based), you can set the `AuthenticationSchemes` collection when adding your policy: +If you prefer to specify the desired schemes in [policy](xref:security/authorization/policies), you can set the `AuthenticationSchemes` collection when adding your policy: ```csharp services.AddAuthorization(options => From bd666067fa3b087d34b3487377575135b3d8efeb Mon Sep 17 00:00:00 2001 From: Scott Addie Date: Mon, 30 Oct 2017 10:51:43 -0500 Subject: [PATCH 4/6] Alphanumeric --> non-alphanumeric (#4668) --- aspnetcore/security/authentication/identity-configuration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnetcore/security/authentication/identity-configuration.md b/aspnetcore/security/authentication/identity-configuration.md index 4ebb2bbcb1..84c306392a 100644 --- a/aspnetcore/security/authentication/identity-configuration.md +++ b/aspnetcore/security/authentication/identity-configuration.md @@ -18,7 +18,7 @@ ASP.NET Core Identity has some default behaviors that you can override easily in ## Passwords policy -By default, Identity requires that passwords contain an uppercase character, lowercase character, a digit, and an alphanumeric character. There are also some other restrictions. If you want to simplify password restrictions, you can do that in the `Startup` class of your application. +By default, Identity requires that passwords contain an uppercase character, lowercase character, a digit, and a non-alphanumeric character. There are also some other restrictions. If you want to simplify password restrictions, you can do that in the `Startup` class of your application. # [ASP.NET Core 2.x](#tab/aspnetcore2x) From 16d9cb4799457ac246193cb5b6162f41c88f3f08 Mon Sep 17 00:00:00 2001 From: Michael DePouw Date: Mon, 30 Oct 2017 12:01:46 -0400 Subject: [PATCH 5/6] fix page title (#4666) * fix page title make it Proper case and remove period in the title * Update authenticated-encryption-details.md --- .../implementation/authenticated-encryption-details.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/aspnetcore/security/data-protection/implementation/authenticated-encryption-details.md b/aspnetcore/security/data-protection/implementation/authenticated-encryption-details.md index ceff18b9c7..9d37c0624d 100644 --- a/aspnetcore/security/data-protection/implementation/authenticated-encryption-details.md +++ b/aspnetcore/security/data-protection/implementation/authenticated-encryption-details.md @@ -1,5 +1,5 @@ --- -title: Authenticated encryption details. +title: Authenticated encryption details author: rick-anderson description: keywords: ASP.NET Core, @@ -12,7 +12,7 @@ ms.technology: aspnet ms.prod: asp.net-core uid: security/data-protection/implementation/authenticated-encryption-details --- -# Authenticated encryption details. +# Authenticated encryption details From 3636765f020ce31a03bb7011da89e111e6b79914 Mon Sep 17 00:00:00 2001 From: Michael DePouw Date: Mon, 30 Oct 2017 12:03:01 -0400 Subject: [PATCH 6/6] fix bad anchor links (#4662) reference: https://opbuildstorageprod.blob.core.windows.net/report/2017%5C10%5C13%5C6a0d29ae-bb37-09f1-c55a-4cfa862c6784%5CPullRequest%5C201710131248087361-4562%5Cworkflow_report.html?sv=2015-02-21&sr=b&sig=GbG0qgcJNtJMXYbbzHZqcp2BJNdAKtUYmbwoSscw5IY%3D&st=2017-10-13T12%3A50%3A41Z&se=2017-11-13T12%3A55%3A41Z&sp=r --- aspnetcore/security/authorization/introduction.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnetcore/security/authorization/introduction.md b/aspnetcore/security/authorization/introduction.md index 2aec46e157..2a480418b5 100644 --- a/aspnetcore/security/authorization/introduction.md +++ b/aspnetcore/security/authorization/introduction.md @@ -22,7 +22,7 @@ Authorization is orthogonal and independent from authentication, which is the pr ## Authorization Types -ASP.NET Core authorization provides a simple declarative [role](roles.md#security-authorization-role-based) and a [rich policy based](policies.md#security-authorization-policies-based) model. Authorization is expressed in requirements, and handlers evaluate a user's claims against requirements. Imperative checks can be based on simple policies or policies which evaluate both the user identity and properties of the resource that the user is attempting to access. +ASP.NET Core authorization provides a simple declarative [role](roles.md) and a [rich policy based](policies.md) model. Authorization is expressed in requirements, and handlers evaluate a user's claims against requirements. Imperative checks can be based on simple policies or policies which evaluate both the user identity and properties of the resource that the user is attempting to access. ## Namespaces