I suggest you ...

Use claims for authorization checks

As a developer I want to be able to leverage a ClaimsPrincipal for the authorization checks using the Security Application Block. The claims that are recognized as identity or roles should tie into the authorization providers (AuthorizationRuleProvider and AzManAuthorizationProvider). Currently the AzMan provider seems dependent on Windows identities.

102 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Alex ThissenAlex Thissen shared this idea  ·   ·  Admin →

    2 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • MarcoslimagonMarcoslimagon commented  · 

        @Anonymous @Alex I think NetSqlAzman has been doing a great job, and it's not fully dependent to Windows Indentyties.. I'm also a AzMan fan.

        They are similar to current AzMan from Entlib

      • Anonymous commented  · 

        The whole store around Authorization should be simplified and provided as a managed solution for .NET. Currently, AzMan is not well published and popular in the .NET world and also, it is not a managed solution.

      Feedback and Knowledge Base