AppFuseSecurity |
|
Your trail: |
Difference between
version 30
and
version 26:
At line 1 changed 1 line. |
This page is a starting point for [AppFuse] related security issues, tutorials and how to's. |
This page is a starting point for [AppFuse] related security issues, tutorials and how to's. As of 1.8, AppFuse uses [Acegi Security|http://acegisecurity.sourceforge.net] for authentication and authorization. In 1.7 and prior, container-managed authentication (CMA) was used. You can revert to CMA if you prefer. |
At line 3 changed 3 lines. |
* How to migrate your pre-AppFuse 1.8 application to use [Acegi Security|http://acegisecurity.sourceforge.net] [authentication|AppFuseAuthentication] |
* How to use [Acegi Security|http://acegisecurity.sourceforge.net] Method Invocation authorization|AppFuseSecurityMethods] |
* How to use [Acegi Security|http://acegisecurity.sourceforge.net] Access Control List authorization|AppFuseSecurityACL] |
* How to migrate your pre-AppFuse 1.8 application to [use Acegi Security for authentication|AppFuseAuthentication]. |
* How to use Acegi Security for [securing methods by role|AppFuseSecurityMethods]. |
* How to use Acegi Security to [control access to objects with ACLs|AppFuseAcegiACL]. |
Back to AppFuseSecurity,
or to the Page History.
|