blocks|key|3033218|text|这个问题以前已经被问过并回答过了：ASP.NET+MVC+-+Set+custom+IIdentity+or+IPrincipal|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3033219|但总而言之...|3033220|使用要存储的其他属性创建自定义主体类：|3033221|Public+Class+CustomPrincipal
++++Inherits+System.Security.Principal.GenericPrincipal

++++Private+_eyeColor+As+String
++++Public+ReadOnly+Property+EyeColor+As+String
++++++++Get
++++++++++++Return+_eyeColor
++++++++End+Get
++++End+Property

++++Public+Sub+New(id+As+System.Security.Principal.IIdentity,+roles+As+String(),+eyeColor+As+String)
++++++++MyBase.New(id,+roles)
++++++++_eyeColor+=+eyeColor++++++++++++
++++End+Sub

End+Class|code-block|syntax|javascript|3033222|修改global.asax+Global.Application_AuthenticateRequest以使用您的自定义主体：|3033223|Protected+Sub+Application_AuthenticateRequest(ByVal+sender+As+Object,+ByVal+e+As+System.EventArgs)
++++...
++++Dim+roles()+As+String+=+{"examplerole"}+++++++++
++++Context.User+=+new+CustomPrincipal(Context.User.Identity,+roles,+"green")
End+Sub|3033224|然后，在代码中的其他地方，当您想引用这些属性之一时，请执行以下操作：|3033225|CType(My.User.CurrentPrincipal,+CustomPrincipal).EyeColor|3033226|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/1064271/asp-net-mvc-set-custom-iidentity-or-iprincipal^0|H|1C|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@$A|13|B|14|1|15]]|C|$]]|$1|D|3|E|5|6|7|16|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|17|8|@]|9|@]|C|$]]|$1|H|3|I|5|J|7|18|8|@]|9|@]|C|$K|L]]|$1|M|3|N|5|6|7|19|8|@]|9|@]|C|$]]|$1|O|3|P|5|J|7|1A|8|@]|9|@]|C|$K|L]]|$1|Q|3|R|5|6|7|1B|8|@]|9|@]|C|$]]|$1|S|3|T|5|J|7|1C|8|@]|9|@]|C|$K|L]]|$1|U|3|-4|5|6|7|1D|8|@]|9|@]|C|$]]]|V|$W|$5|X|Y|Z|C|$10|11]]]]

This question has been asked and answered before:
<a href="https://stackoverflow.com/questions/1064271/asp-net-mvc-set-custom-iidentity-or-iprincipal">ASP.NET MVC - Set custom IIdentity or IPrincipal</a>

But to summarize...

Crate a custom principal class with the additional properites you want to store:

<pre><code>Public Class CustomPrincipal
 Inherits System.Security.Principal.GenericPrincipal

 Private _eyeColor As String
 Public ReadOnly Property EyeColor As String
 Get
 Return _eyeColor
 End Get
 End Property

 Public Sub New(id As System.Security.Principal.IIdentity, roles As String(), eyeColor As String)
 MyBase.New(id, roles)
 _eyeColor = eyeColor 
 End Sub

End Class
</code></pre>

Modify global.asax Global.Application_AuthenticateRequest to use your custom principal:

<pre><code>Protected Sub Application_AuthenticateRequest(ByVal sender As Object, ByVal e As System.EventArgs)
 ...
 Dim roles() As String = {"examplerole"} 
 Context.User = new CustomPrincipal(Context.User.Identity, roles, "green")
End Sub
</code></pre>

Then elsewhere in your code when you want to refer to one of these properties do this:

<pre><code>CType(My.User.CurrentPrincipal, CustomPrincipal).EyeColor
</code></pre>

blocks|key|302358|text|你不能真的期望别人能在几个段落里教你所有你不知道的关于.NET的东西。你可以在MSDN+http://msdn.microsoft.com/en-us/library/system.security.principal.genericprincipal.aspx上读到非常好的例子，并深入研究这个类和它在Reflector中的派生--没有什么特别的。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|302359|角色只是在你的应用程序/服务器中供你自己使用的名称的字符串阵列。|302360|话虽如此，你实际上并不一定要瞄准确切的GenericPrincipal推导。检查|302361|HttpContext.Current.Items|code-block|syntax|javascript|302362|它是一个免费使用的Hashtable，仅用于您正在服务的请求-这意味着您可以在某一点上这样做：|302363|HttpContext.Current.Items["TokenUser"]+=+new+MyThinUser(anything,I,want,there);|302364|然后代码中的所有其他部分都会这样做：|302365|var+user+=+HttpContext.Current.Items["TokenUser"]+as+MyThinUser;|302366|你就完了。|302367|在新类中存储您需要/想要传递的所有内容，从身份验证代码到所有其他函数。保持用户属性不变(这样您就可以窥视它，而不必担心您更改了某些内容)。你可以随意简化或复杂化你的系统，但你要保持完全的独立性。|302368|例如，如果您有自己的身份验证，并且只有几个级别的访问，而不是枚举角色，那么您可以只携带良好的旧访问级别编号(枚举角色作为字符串携带是非常低效的)。|302369|请记住，VS中的自生成样本通常是针对某些特定场景的。因此，如果您看到SQL提供程序用于用户管理，这并不意味着您实际上必须使用它-您仍然可以调用自己的存储过程来从您自己的SQL表中获取所需的内容。|302370|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/system.security.principal.genericprincipal.aspx^0|18|2F|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@$A|1B|B|1C|1|1D]]|C|$]]|$1|D|3|E|5|6|7|1E|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|1F|8|@]|9|@]|C|$]]|$1|H|3|I|5|J|7|1G|8|@]|9|@]|C|$K|L]]|$1|M|3|N|5|6|7|1H|8|@]|9|@]|C|$]]|$1|O|3|P|5|J|7|1I|8|@]|9|@]|C|$K|L]]|$1|Q|3|R|5|6|7|1J|8|@]|9|@]|C|$]]|$1|S|3|T|5|J|7|1K|8|@]|9|@]|C|$K|L]]|$1|U|3|V|5|6|7|1L|8|@]|9|@]|C|$]]|$1|W|3|X|5|6|7|1M|8|@]|9|@]|C|$]]|$1|Y|3|Z|5|6|7|1N|8|@]|9|@]|C|$]]|$1|10|3|11|5|6|7|1O|8|@]|9|@]|C|$]]|$1|12|3|-4|5|6|7|1P|8|@]|9|@]|C|$]]]|13|$14|$5|15|16|17|C|$18|19]]]]

You can't realy expect that someone can teach you everything you don't know about .NET in a few paragraphs. You can read pretty good example at MSDN <a href="http://msdn.microsoft.com/en-us/library/system.security.principal.genericprincipal.aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/library/system.security.principal.genericprincipal.aspx</a> and dig through the class and it's derivatives in Reflector - there's nothing spectacularly special about it.

Roles are just a string arrray of names for your own use, in your app/server.

Having said that, you don't really have to aim at exact GenericPrincipal derrivative at all. Check out 

<pre><code>HttpContext.Current.Items
</code></pre>

It's a Hashtable for free use just for the request you are servicing - meaning that at one point you can do say:

<pre><code>HttpContext.Current.Items["TokenUser"] = new MyThinUser(anything,I,want,there);
</code></pre>

and then everythere else in the code just do:

<pre><code>var user = HttpContext.Current.Items["TokenUser"] as MyThinUser;
</code></pre>

and you are done.

Store in your new class everything you need/want to pass around from the authentification code to all other functions. Leaves User property intact (so you can peek into it and not have to worry that you changed something). Wihr that you can simplify or complicate your system at will but you keep full independence. 

For example if you have your own authentification and just a few levels of acces instead of enumerated roles you can just carry good old access level number (enumerated roles carried around as strings are very inefficient anyway).

Keep in mind that autogenned samples in VS are usually geared towards some particular scenario. So if you see SQL providers for user management that doesn't mean that you actually have to use it - you can still just call your own sproc to get what you need from your own table in SQL.

I want to store extra information in the authenticated user so that I can have it easily accessible (like User.Identity.Id, for example), instead of just the name, since I'm planning on having that non-unique. 

So far I've gathered that I should look to implement custom Principal and/or Identity, but I'm not sure how to go about it. I've been looking for documentation and tutorials on the matter, but I've found related stuff in different places and I've found it a bit confusing.

I have seen how to add custom info to the authentication cookie in the user data property, but I'd like to have the benefit of dependency injection for unit testing, which I can have with the principal and identity.

What are the exact steps I need to consider if I want to implement my own Principal or Identity?

What would be the simplest I could do in this scenario (just add the ID and keep all the defaults in place)? "Defaults" would include the default providers (membership, roles, etc.). 

I have seen the <a href="https://stackoverflow.com/questions/1064271/asp-net-mvc-set-custom-iidentity-or-iprincipal">other question</a>, but I'd appreciate answers that do not leave any holes in between, such as the roles magic strings in the AuthenticateRequest event in the examples. Instead I need to know how to add the roles from the default SqlRoleProvider to the current user: when and where to do it, and if I need to do anything else to connect my new classes with the other default providers. 

It'd be awesome to be able to go to a sample ASP.NET MVC 2 application (from the visual studio 2010 template, for example), make the edits and have it work.

<hr>

EDIT: I have edited the question to better show that I'm pretty much lost here, so I can't make do with too high level answers. 

P.S.: It seems to me that it makes more sense to have the ID in the Identity instead of the principal, although I have, in a way, stated this before.

How do I implement custom Principal and Identity in ASP.NET MVC?

身份验证

单元测试

服务器

我希望在经过身份验证的用户中存储额外的信息，这样我就可以轻松地访问它(例如，像User.Identity.Id )，而不仅仅是名称，因为我计划让它不是唯一的。到目前为止，我已经了解到我应该考虑实现自定义主体和/或标识，但我不确定如何进行。我一直在寻找关于这个问题的文档和教程，但我在不同的地方找到了相关的东西，我发现它有...

问如何在ASP.NET MVC中实现自定义的主体和标识？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在ASP.NET MVC中实现自定义的主体和标识？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在ASP.NET MVC中实现自定义的主体和标识？
EN