Integration with .NET 4.5 WIF ClaimsAuthorizationManager

Topics: General Topic, NetSqlAzMan Core
Jan 25, 2013 at 3:18 PM

I am very interested in how we can use NetSqlAzMan to act as a ClaimsAuthorizationManager as part of an overall architecture that uses AD for authentication with ADFS acting as an STS and NetSqlAzMan providing the authorization rules policy engine.

Is it possible for authorization decisions to be made by .NetSqlAzman by creating a custom class inheriting from ClaimsAuthorizationManager and passing the AuthorizationContext in?

Peviousy I have read that there is a problem with NetSqlAzman only supporting WindowsIdentity however since the hierarchy of IIdentity has been changed in .NET 4.5 perhaps this is now possible?

I have been looking for guidance on how to work alongside Windows Identity Foundation since there is no concrete implementaiton of a ClaimsAuthorizationManager included in the framework and there appears to be very limited information on how one might be created.


I am honestly amazed that Microsoft have not shipped an implementaiton of an authorizationmanager however perhaps this is a great opportunity for .NetSqlAzMan to fill that gap?


Jan 28, 2013 at 11:42 AM

But NetSqlAzMan is based on .NET 4.0 ... so we can do what you are saying only after .NET 4.5 porting.


Jan 28, 2013 at 12:47 PM

Thanks for replying however a few more details would be useful!

Are there plans to upgrade to .NET 4.5? 

If you read around this subject there is a lot of traction for WIF integration but it is missing the ClaimsAuthorization component and I think that .NETSqlAzMan may be a perfect fit and therefore a great opportunity to get a lot more users on-board. However these potential users will be looking for some guidance and scenarios which at the moment are nowhere to be seen.



Feb 11, 2013 at 11:42 AM
Any chance of an update on this question?
Feb 11, 2013 at 2:05 PM
By now there is no plan to upgrade to. net 4.5 and no integration with WIF.

Unfortunately, my time has been reduced a lot.
I'm sorry.

Feb 12, 2016 at 8:30 PM

If there are no plans to port this project to FW 4.5 and incorporate WIF to form a hybrid solution. Can you describe what I would need as a minimal implementation using the SQL Store?

Right now the mindset is to bank on the effort invested (roles, tasks and operations) by changing the storage and incorporate WIF. The tasks and operations provide the granularity that we seek, while WIF opens the doors to the future by allowing us to retarget your code.

Application -----
                      |------- WIF -----
                                                |------- NetSqlAzMan
The application would use the WIF Claims Manager which sits on the NetSqlAzMan engine.