Re: Authorization problem
From: Nikolay Petrov (johntup2_nospam__at_mail.bg)
Date: Tue, 26 Oct 2004 18:59:06 +0300
Never heard of reflection ;-)
how to do?
"Joe Kaplan (MVP - ADSI)" <firstname.lastname@example.org> wrote
in message news:emupGP3uEHA.2116@TK2MSFTNGP14.phx.gbl...
> One other thing to check:
> Can you do a programmatic check instead of a declarative one? Try
> Context.User.IsInRole("machine\administrators") or
> Those should do the same thing as the declarative demand, but it is worth
> a shot.
> Another thing to try is to use reflection on _GetRoles private method on
> WindowsIdentity to see what the actual values are. This can be helpful
> for troubleshooting Windows group resolution. Don't use this in
> production though!
> Google will dig up a bunch of code samples showing how to do that if you
> need it.
> Joe K.
> "Nikolay Petrov" <email@example.com> wrote in message
>>I have done that. It is fine.
>> Something else is broken. The auditing don't show nothing also.
>> "Joe Kaplan (MVP - ADSI)" <firstname.lastname@example.org>
>> wrote in message news:efhvF42uEHA.1976@TK2MSFTNGP09.phx.gbl...
>>> Are you certain that the client is being authenticated with Windows
>>> authentication? It would probably be a good idea to dump out the value
>>> of Context.User.Identity.Name and make sure it is the user that you
>>> think it is.
>>> Joe K.