Re: AzMan concurrency.
From: Palo Mraz (palo_at_lamarvin.com)
Date: 02/21/05
- Next message: Palo Mraz: "Re: Application-Managed Authorization"
- Previous message: Sosa: "RE: Distributed Application Design using .NET"
- Maybe in reply to: Morten Overgaard: "Re: AzMan concurrency."
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 21 Feb 2005 10:37:40 +0100
Claudio,
Storing authorization policies in a database seems to be the only
tried-and-true way to ensure data integrity in a multi-user environment,
IMHO (perhaps using the "serializable" transaction isolation level). If
you'd like to combine SQL Server storage with declarative authorization
policies, let me kindly ask you to review our Constable Authorization
Manager (CAZE) library - a 100% managed, XML-based authorization library for
.NET applications. CAZE authorization policies are represented as XML
strings that can be stored in a database. The CAZE authorization policy
leverages the .NET's role-based authorization model and it allows you to
easily blend Windows groups with custom authorization logic (even COM+ roles
are supported out of the box). For more information, please see the CAZE
website: http://www.lamarvin.com/caze_default.asp, or contact me directly:
palo@lamarvin.com.
Best regards,
Palo Mraz
PS: I'm hoping that this plug about CAZE doesn't violate the MS newsgroups
rules of conduct. If it does, please forgive me and let me know so I won't
do that in the future.
- Next message: Palo Mraz: "Re: Application-Managed Authorization"
- Previous message: Sosa: "RE: Distributed Application Design using .NET"
- Maybe in reply to: Morten Overgaard: "Re: AzMan concurrency."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|