WindowsIdentity is not going to help you.
I'm not sure about this but just an idea - could DirectorySearcher help you?
Or maybe calling native code to get this information?
-jas
WindowsIdentity in .NET 2.0 actually helps a lot as it now as a Groups
property. However, that is hidden in the internal class state in .NET 1.x.
You can use reflection to hack it out though.
If you want to retrieve group membership via LDAP, then you want to use
System.DirectoryServices. Ryan's blog posting has a pretty good sample on
the right way to do transitive group membership expansion.
http://dunnry.com/blog/CategoryView.aspx?category=DirectoryServices#a4174a2c1-d1
05-4fbb-ab86-40bd2ab53da6
The reason the WindowsIdentity "UPN" constructor probably isn't working is
that it requires 2003 domain controllers and must be executed on a 2003
server as well. It is uses a new feature called Protocol Transition, or S4U
Kerberos, to create the WindowsIdentity, and those APIs only exist in 2003.
Joe K.
> WindowsIdentity is not going to help you.
>
[quoted text clipped - 17 lines]
>>
>> Any code would help, please.
Dominick Baier [DevelopMentor] - 26 Oct 2005 12:36 GMT
Hello Joe,
yeah - there is a hack available for 1.1
you can find it here:
http://weblogs.asp.net/pglavich/archive/2004/09/29/235670.aspx
the code shown there does not work under 2.0 anymore, so be careful - or
use P/Invoke directly.
---------------------------------------
Dominick Baier - DevelopMentor
http://www.leastprivilege.com
> WindowsIdentity in .NET 2.0 actually helps a lot as it now as a Groups
> property. However, that is hidden in the internal class state in .NET
[quoted text clipped - 39 lines]
>>> their current permissions (roles).
>>> Any code would help, please.