Comments on: T4 Toolbox: Strongly-typed AzMan wrapper generator

By: Oleg Sych

Oleg Sych — Sun, 28 Dec 2008 20:40:38 +0000

Good point, Jeff. Thanks for bringing this up. Can you share any practical reasons to deploy AzMan authorization policy in production to Active Directory or SQL as opposed to an XML file?

By: Jeff Odell

Jeff Odell — Sun, 28 Dec 2008 19:34:05 +0000

One additional comment - while Oleg provides instructions to deploy the Authorization Policy XML file, the XML file is really provided as a developer tool.

Actual enterprise implementations will use either Active Directory (typically via an Application Directory Application Mode instance) or, with Windows Server 2008 and/or Vista, SQL Server as the backing store for the Application Policy.

None of this affects the generation process; generating from the XML file is still valid, but deployment of would likely be to load the XML file into one of the other backing stores.

By: Jeff Odell

Jeff Odell — Sun, 28 Dec 2008 18:25:08 +0000

Going from memory it has an XML file that you can import and export from their MMC snap in. So the same pattern you created for AzMan should work.

I already have the equivalent “Check Operation” code integrated into a proof of concept – it isn’t a COM call of course – it calls the library that in turn uses LINQ to SQL.

By: Oleg Sych

Oleg Sych — Sun, 28 Dec 2008 16:26:10 +0000

Thanks for mentioning this product, Jeff. I glanced over the documentation on SourceForge, it looks like the API is comparable to AzMan’s, so it should be possible. How are you planning to store the authorization policy during development? Does NetSqlAzMan allow using XML files?

By: Jeff Odell

Jeff Odell — Sun, 28 Dec 2008 15:31:34 +0000

Nice - my new project is using the .Net SQL Authorization Manager; (http://sourceforge.net/projects/netsqlazman/). We should be able to reuse the ideas in this template to support that tool.