Re: Client Windows Application Role based Security

From: Joe Kaplan \(MVP - ADSI\) (joseph.e.kaplan_at_removethis.accenture.com)
Date: 07/13/04

  • Next message: mei xiao: "triple des in openSSL" 
    Date: Tue, 13 Jul 2004 14:42:39 -0500

    You can use the .NET Framework built-in IPrincipal::IsInRole stuff. It
    gives you much less power and flexibility than AzMan does, but it is
    built-in and might be sufficient.

    To make IPrincipal tie in with Windows security in a forms app, you need to
    change the principal policy on your AppDomain to Windows, but after that, it
    will just work.

    Joe K.

    "Henrik Skak Pedersen" <hsp@circlecapital.com> wrote in message
    news:ub9H%23hQaEHA.3716@TK2MSFTNGP11.phx.gbl...
    > Short correction, I should be azroles.dll instead of AzMan.dll Sorry!
    >
    > "Henrik Skak Pedersen" <hsp@circlecapital.com> wrote in message news:...
    > > Hi,
    > >
    > > I am developing a windows application and I need some kind of role based
    > > security. I have been looking a little at Authorization Manager and I
    > think
    > > that it looks very nice og I have almost decided to use it. I just have
    > some
    > > questions before I move on.
    > >
    > > 1) It Authentication Manager the right way to go when you are developing
    > > windows applications?
    > >
    > > 2) What are the alternatives?
    > >
    > > 3) None of my clients would propably be Windows 2003 servers or Windows
    XP
    > > with Administrative Tools installed. So how do I call the Authorization
    > > Manager? Do I need to redistribute the AzMan.dll or do I call a Web
    > Service
    > > which handle the authentication?
    > >
    > > 4) I have tried to run Keith Browns example on my Windows XP and I got
    > some
    > > problems with the Microsoft.Interop.Security.AzRoles reference. I have
    > read
    > > in a questions from another guy that I on Windows XP needed to reference
    > the
    > > AzMan.dll in Windows\system32, I the did that but I still got the
    problem.
    > I
    > > then figured out that I also needed to change the namespace in my code
    > from
    > > Microsoft.Interop.Security.AzRoles to AZROLESLib and then it worked.
    Would
    > > that not give me problems when I run my code on a Windows 2003 server?
    > >
    > >
    > > Best regards
    > >
    > > Henrik Skak Pedersen
    > >
    > >
    >
    >

  • Next message: mei xiao: "triple des in openSSL"

    Relevant Pages

    • RE: Memory Full Problem
      ... I ran Spybot Search and Destroy after updating and imunizing my computer. ... connections through the Windows Firewall. ... Product: Windows Security Center ... Internet Explorer 6 with Windows XP Home Edition SP 2. ...
      (microsoft.public.windowsxp.newusers)
    • Re: Access Control Models
      ... DAC and CAS models. ... The Windows 2000 Authorization Manager Runtime is a Windows 2000 Server ... version of the Windows Server 2003 Authorization Manager Role-Based ...
      (microsoft.public.security)
    • Re: Access Control Models
      ... W2k3 release time of how the CAS model from .Net could grow to ... The Windows 2000 Authorization Manager Runtime is a Windows 2000 Server ... version of the Windows Server 2003 Authorization Manager Role-Based ...
      (microsoft.public.security)
    • Re: Access Control Models
      ... DAC and CAS models. ... The Windows 2000 Authorization Manager Runtime is a Windows 2000 Server ... version of the Windows Server 2003 Authorization Manager Role-Based ...
      (microsoft.public.security)
    • Re: Access Control Models
      ... Blow has sensitive data on his computer because of DAC he can give ANY ... The Windows 2000 Authorization Manager Runtime is a Windows 2000 Server ... version of the Windows Server 2003 Authorization Manager Role-Based ...
      (microsoft.public.security)
    • Quantcast