Is there a replacement for Azman, that is a new way to apply security. Previously we were using EntLib 3 and used Azman for our security and authorisation. However an article I read about the vision of EntLib 6.0 is to deprecate Security(link below), but there is no alternative specified. May someone please advise what the best method to handle security and authorization is now?
edit: Azman seems deprecated on Windows 2012 R2, see the first link
AzMan itself is NOT deprecated and is available for modern versions of Windows, including Windows Server 2012 and Windows 8. What is deprecated is the EntLib’s Security Application Block which included a wrapper to AzMan. This is aligned with our deprecation approach.
You have several options depending on your upgrade objectives:
- Upgrade to EntLib5.0 which still includes the Security Application Block with AzMan wrapper.
- Use AzMan directly.
- Upgrade to EntLib 6, but take the source of AzMan wrapper from EntLib5.
- Use claims-based authorization though that’s a very different model. For more info, I suggest you take a look at this Guide to Claims-Based Identity.
In terms of migrating to a claims-based approach, have a look at:
Claims : Azman in the new claims-based world.
Note Azman is deprecated as of Windows Server 2012 R2 and may be removed in subsequent versions.
recovering this question, and kind of stuck. I have a WCF .Net framework 4.0 project that takes advantage of AzMan for authorization purposes.
We are thinking of migrating this project to .Net 6, but we need to keep using some sort of authorization with Active Directory, but AzMan is not an option nowadays.
What is a possible evolution in order to replace azman for this scenario?
© 2022 - 2024 — McMap. All rights reserved.