Here are some of the external pages mentioning Acegi Security. If you've found another, please let us know.
Let's assuming you're developing an enterprise application based on Spring. +
Let's assume you're developing an enterprise application based on Spring. There are four security concerns you typically need to address: authentication, web request security, service layer security (ie your methods that implement business logic), and domain object instance security (ie different domain objects @@ -102,8 +102,8 @@ so would introduce an additional argument on every services layer method. A more elegant approach is to use a ThreadLocal to hold the Principal, although this would likely increase - development time to a point where it would become more e - conomical (on a cost-benefit basis) to simply use a dedicated + development time to a point where it would become more + economical (on a cost-benefit basis) to simply use a dedicated security framework.
AuthenticationDao implementations that simply don't properly
implement the interface. For example, they return null instead
of the user not found exception, or fail to add in the
- GrantedAuthority[]s. We suggest you write the
- UserDetails object generated by your AuthenticationDao
- to the log and check it looks correct.
+ GrantedAuthority[]s. Whilst DaoAuthenticationProvider
+ does its best to check the AuthenticationDaoreturns a valid
+ UserDetails, we suggest you write the
+ UserDetails object to the log and check it looks correct.
The most important things to post with any support requests on the @@ -208,7 +209,7 @@ Log4J (instead of JDK logging), Tapestry (instead of JSF), and Velocity/FreeMarker (instead of JSP). It's important to recognise that many open source projects do develop into de facto standards, and in doing so play a legitimate and beneficial - role in the software development profession.
+ role in professional software development.Yes. If you've written something and it works well, please feel free to share it.