blocks|key|2916058|text|如果你正在寻找一个样例项目，目前还没有那么多。首先要查看的地方是aspnet+GitHub项目页面。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2916059|幸运的是，ASP.NET+Identity子项目有一个样例项目，您可以查看一下here，但是它可能没有涵盖您的所有需求。请注意，这使用的是最新的测试版。|2916060|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/aspnet|1|https://github.com/aspnet/Identity/tree/dev/samples/IdentitySample.Mvc^0|W|6|0|0|13|4|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

If you are looking for a sample project there are not that many out there at the moment. The first place to look is on the <a href="https://github.com/aspnet" rel="nofollow">aspnet</a> GitHub project pages.

Luckily, the ASP.NET Identity sub-project has a sample project that you can take a look at <a href="https://github.com/aspnet/Identity/tree/dev/samples/IdentitySample.Mvc" rel="nofollow">here</a>, however it may not cover all your requirements. Note that this is using the latest beta.

blocks|key|136928|text|我们在这里是同一条船，当然除了源代码之外没有太多的阅读……|type|unstyled|depth|inlineStyleRanges|entityRanges|data|136929|我们最终实现了政策。保单是需要授权才能满足的一组索赔。然后可以将这些策略应用于控制器。|136930|您可以在Startup.cs、ConfigureServices中定义您的策略：|136931|services.AddAuthorization(options+=>
{
++++options.AddPolicy("SalesSenior",+policy+=>
++++{
++++++++policy.RequireClaim("department",+"sales");
++++++++policy.RequireClaim("status",+"senior");
++++});
});|code-block|syntax|javascript|136932|我们定义了角色，为他们分配了一个或多个声明，并为用户分配了角色，允许他们在点击控制器时根据适当的策略进行检查。|136933|您可以将IAuthorizationService注入控制器或属性，如下所示：|offset|length|style|CODE|136934|public+class+SalesDashboardController:+Controller
{
++++private+readonly+IAuthorizationService+_authz;

++++public+VarianceOverviewController(IAuthorizationService+authz)
++++{
++++++++_authz+=+authz;
++++}
++++...
}|136935|然后，您可以使用IAuthorizationService检查用户声明的有效性...|136936|if+(await+_authz.AuthorizeAsync(User,+"SalesSenior"))
{
++++//+User+is+authorized++++++++++++
}|136937|This+article是我这篇文章的主要来源，对我来说是一个很好的入门读物。祝好运!|136938|entityMap|0|LINK|mutability|MUTABLE|url|http://leastprivilege.com/2015/10/12/the-state-of-security-in-asp-net-5-and-mvc-6-authorization/^0|0|0|0|0|0|4|L|0|0|8|L|0|0|0|C|0|0^^$0|@$1|2|3|4|5|6|7|18|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|19|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1A|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|1B|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|1C|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1D|8|@$O|1E|P|1F|Q|R]]|9|@]|A|$]]|$1|S|3|T|5|H|7|1G|8|@]|9|@]|A|$I|J]]|$1|U|3|V|5|6|7|1H|8|@$O|1I|P|1J|Q|R]]|9|@]|A|$]]|$1|W|3|X|5|H|7|1K|8|@]|9|@]|A|$I|J]]|$1|Y|3|Z|5|6|7|1L|8|@]|9|@$O|1M|P|1N|1|1O]]|A|$]]|$1|10|3|-4|5|6|7|1P|8|@]|9|@]|A|$]]]|11|$12|$5|13|14|15|A|$16|17]]]]

We were in the same boat here, without much in terms of reading apart from the source of course...

We ended up implementing Policies. Policies being a group of Claims that are required for authorization to be satisfied. these Policies can then be applied to Controllers.

You can define your Policies in Startup.cs, ConfigureServices:

<pre><code>services.AddAuthorization(options =&gt;
{
 options.AddPolicy("SalesSenior", policy =&gt;
 {
 policy.RequireClaim("department", "sales");
 policy.RequireClaim("status", "senior");
 });
});
</code></pre>

We defined Roles, assigned 1 or more Claims to them and assigned Roles to Users allowing them to be checked against the appropriate Policy on hitting a Controller.

You can inject the <code>IAuthorizationService</code> into a Controller or Attribute as so:

<pre><code>public class SalesDashboardController: Controller
{
 private readonly IAuthorizationService _authz;

 public VarianceOverviewController(IAuthorizationService authz)
 {
 _authz = authz;
 }
 ...
}
</code></pre>

You can then use the <code>IAuthorizationService</code> to check the validity of a users claims...

<pre><code>if (await _authz.AuthorizeAsync(User, "SalesSenior"))
{
 // User is authorized 
}
</code></pre>

<a href="http://leastprivilege.com/2015/10/12/the-state-of-security-in-asp-net-5-and-mvc-6-authorization/" rel="nofollow">This article</a> was my main source for this stuff and was a great primer for me. Good luck!

blocks|key|134609|text|这个帖子帮助我做了一些工作，但令人遗憾的是，没有更好的文档。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|134610|以下是我改进这一点的一些尝试。Asp.net.Identity+(3.0.0.0-rc1-最终)|134611|在Startup.cs+-->+ConfigurationServices中|134612|++++++++//Define+your+policies+here,+they+are+strings+associated+with+claims+types,+that+have+claim+strings...+
++++++++//they+need+to+be+in+AspNetUserClaims+table,+user+id,+department,+Dev+to+be+allowed+access+to+the+Dev+policy
++++++++//add+the+auth+option,+below+that+makes+it+work,+and+in+the+api+controller,+add+the++++++++
++++++++//[Authorize("Dev")]+attribute
++++++++services.AddAuthorization(
++++++++++++options+=>
++++++++++++{
++++++++++++++++options.AddPolicy("Dev",+policy+=>+{+policy.RequireClaim("department",+"Dev");+});
++++++++++++});
++++++++services.AddMvc();|code-block|syntax|javascript|134613|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|O|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|P|8|@]|9|@]|A|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

This thread helped me get something working, but it's sad that this is not better documented.

Here are my attempts at improving that. Asp.net.Identity (3.0.0.0-rc1-final) 

in Startup.cs --> ConfigurationServices

<pre><code> //Define your policies here, they are strings associated with claims types, that have claim strings... 
 //they need to be in AspNetUserClaims table, user id, department, Dev to be allowed access to the Dev policy
 //add the auth option, below that makes it work, and in the api controller, add the 
 //[Authorize("Dev")] attribute
 services.AddAuthorization(
 options =&gt;
 {
 options.AddPolicy("Dev", policy =&gt; { policy.RequireClaim("department", "Dev"); });
 });
 services.AddMvc();
</code></pre>

I'm currently looking for a solution to use an advanced Roles/Group Permission management in ASP .NET 5 MVC 6 with Identity 3. I started a new Preview Starter Web Project with a integrated easy login system.

Now I need a complex "users permission management" with following functions:

<ol>
<li>users can be in multiple groups/roles</li>
<li>a group/role have many access objects (e.g. CanAccessUser, CanEditUser...)</li>
<li>these access objects (maybe claims?) of each group/roles complement each other </li>
<li>(optional for the ultimate solution): additionally => access objects(maybe claims) can be assigned independently by a group to a user</li>
</ol>

I have seen that identity already broadly provides a fitting for me table structure . (e.g. AspNetUsers, AspNetUserRoles, AspNetRoles, AspNetRoleClaims),

But I'm missing a good example / documentation to use them. 

For MVC 5, I used this example: Users have many groups, a group can have many roles (Roles are the Access Objects in source code for classes / functions)
<a href="http://typecastexception.com/post/2014/08/10/ASPNET-Identity-20-Implementing-Group-Based-Permissions-Management.aspx">ASP.NET Identity 2.0: Implementing Group-Based Permissions Management</a>

Exists for these requirements already a working example that you do not have to reinvent the wheel.

ASP .NET 5 MVC 6 Identity 3 Roles Claims Groups

GitHub

现在我需要一个复杂的“用户权限管理”，具有以下功能：用户可以位于多个组/角色中，一个组/角色可以有多个访问对象(例如CanAccessUser、CanEditUser...)these access objects (也许是claims?)(对于终极解决方案是可选的)：此外，组可以将=> access对象(可能是声明)...

问ASP .NET 5 MVC 6 Identity 3角色声明组
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问ASP .NET 5 MVC 6 Identity 3角色声明组EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问ASP .NET 5 MVC 6 Identity 3角色声明组
EN