Re: IsInRole always return fasle on secure remoting call (Framework 2.0)

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: lukezhan@xxxxxxxxxxxxxxxxxxxx (Luke Zhang [MSFT])
Date: Wed, 08 Mar 2006 09:29:38 GMT

Since you have get remote caller's aco*** from
System.Threading.Thread.CurrentPrincipal, you amy authenticate it by query
the AD directly:

How to authenticate against the Active Directory by using Forms
authentication and Visual C# .NET

http://support.microsoft.com/kb/316748

Luke Zhang
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

.

References:
- RE: IsInRole always return fasle on secure remoting call (Framework 2.0)
  - From: Luke Zhang [MSFT]
- Re: IsInRole always return fasle on secure remoting call (Framework 2.0)
  - From: Eric
- Re: IsInRole always return fasle on secure remoting call (Framework 2.0)
  - From: Luke Zhang [MSFT]
- Re: IsInRole always return fasle on secure remoting call (Framework 2.0)
  - From: Eric
- Re: IsInRole always return fasle on secure remoting call (Framework 2.0)
  - From: Luke Zhang [MSFT]
- Re: IsInRole always return fasle on secure remoting call (Framework 2.0)
  - From: Eric

Prev by Date: user interface process application blocks for Framework 2.0
Next by Date: How to pass alternate credentials using remoting 2.0 over tcp channel
Previous by thread: Re: IsInRole always return fasle on secure remoting call (Framework 2.0)
Next by thread: Re: DataTable to String
Index(es):
- Date
- Thread