Now, we said that application security was about authentication—controlling who accessed your application—as well as about authorization—controlling what folk who were permitted access would be allowed to do. ADAM and MIIS are the tools for helping you meet the first requirement, that of authenticating users of the application. The Windows Server 2003 Authorization Manager is a new tool for helping you meet the second requirement, that of authorization, controlling what users of the application are permitted to do. In that capacity, Authorization Manager joins some older technologies for authorization, which are access control lists, COM+ role-based security, and the facilities of the System.Security.Principal namespace of the .NET Framework Class Library.
[This posting is provided "AS IS" with no warranties, and confers no rights.]