Group items tagged

1.3.What Java and Spring Framework versions are required?

Spring Security 3.0 and 3.1 require at least JDK 1.5

Domain object instance security: In many applications it's desirable to define Access Control Lists (ACLs) for individual domain object instances. We provide a comprehensive ACL package with features including integer bit masking, permission inheritance (including blocking), an optimized JDBC-backed ACL repository, caching and a pluggable, interface-driven design.

OpenID Support: the web's emerging single sign-on standard (supported by Google, IBM, Sun, Yahoo and others) is also supported in Spring Security

Easy integration with existing databases: Our implementations have been designed to make it easy to use your existing authentication schema and data (without modification). Of course, you can also provide your own Data Access Object if you wish. Password encoding: Of course, passwords in your authentication repository need not be in plain text. We support both SHA and MD5 encoding, and also pluggable "salt" providers to maximise password security.

Spring Security Dependencies

This appendix provides a reference of the modules in Spring Security and the additional dependencies that they require in order to function in a running application

C.1 spring-security-coreThe core module must be included in any project using Spring Security.

ComparisonThis section provides a brief comparison of SAFs functionality with that of the Acegi Security Framework [11] and JBoss Seam Security [12]

Acegi’s Policy Decision functionality is not based on Java security standards but on a proprietary solution

ACL defines per domain object who has access permissions

Spring Security

However, it is tied to the Spring technology and the size of the library — more than 10 JAR of dependencies