This link has been bookmarked by 27 people . It was first bookmarked on 23 Apr 2008, by Lubos Pochman.
-
29 Jan 11
bonryk bonryko now we have setup the database based resources and now the next step is to get Spring Security to read the user details from the database. The examples that come with Spring Security 2.0 shows you how to keep a list of users and authorities in the confi
-
14 Jul 10
-
29 Mar 10
-
27 Oct 09
Michal BuczkoFormerly called ACEGI Security for Spring, the re-branded Spring Security 2.0 has delivered on its promises of making it simpler to use and improving developer...
-
05 Feb 09
-
09 Jan 09
-
24 Aug 08
-
21 Aug 08
-
07 Aug 08
-
07 Jul 08
-
- Substantially simplified configuration.
- OpenID integration, single sign on standard.
- Windows NTLM support, single sign on against Windows corporate networks.
- Support for JSR 250 ("EJB 3") security annotations.
- AspectJ pointcut expression language support.
- Comprehensive support for RESTful web request authorization.
- Long-requested support for groups, hierarchical roles and a user management API.
- An improved, database-backed "remember me" implementation.
- New support for web state and flow transition authorization through the Spring Web Flow 2.0 release.
- Enhanced WSS (formerly WS-Security) support through the Spring Web Services 1.5 release.
- A whole lot more...
-
-
18 Jun 08
-
17 Jun 08
-
By default, the <jdbc-user-service> requires the following tables: user, authorities, groups, group_members and group_authorities.
-
By adding the users-by-username-query and authorities-by-username-query properties you are able to override the default SQL statements with your own.
-
-
04 May 08
-
26 Apr 08
-
25 Apr 08
-
23 Apr 08
-
Emmanuel HugonnetThis article outlines how to convert your existing ACEGI based Spring application to use Spring Security 2.0.
-
22 Apr 08
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.