Spring Security 3.

Transcription

1 Spring Security 3 1. Introduction 2. Security Namespace Configuration Web.xml configuration: <filter> </filter> <filter-name>springsecurityfilterchain</filter-name> <filter-class>org.sf.web.filter.delegatingfilterproxy</filter-class> <filter-mapping> <filter-name>springsecurityfilterchain</filter-name> <url-pattern>/*</url-pattern> </filter-mapping> To enable web security: (in applicationcontext-security.xml) <http auto-config='true'> <intercept-url pattern="/**" access="role_user" /> <intercept-url pattern="/login.jsp*" access="is_authenticated_anonymously"/> </http> The prefix ROLE_ is a marker which indicates that a simple comparison with the user's authorities should be made. To add the users: <authentication-manager> <authentication-provider ref="ldapauthenticationprovider"/> </authentication-manager> or <authentication-manager> <authentication-provider> <user-service> <user name="jimi" password="xxx" authorities="role_user" />

2 </user-service> </authentication-provider> </authentication-manager> Default logout URL: j_spring_security_logout To force HTTPS: <intercept-url pattern="/secure/**" access=" " requires-channel="https"/> Annotation-based security: <global-method-security secured-annotations="enabled" /> 3. Sample Applications 4. Spring Security Community 5. Technical Overview SecurityContextHolder, to provide access to the SecurityContext. SecurityContext, to hold the Authentication and possibly request-specific security information. Authentication, to represent the principal in a Spring Security-specific manner. GrantedAuthority, to reflect the application-wide permissions granted to a principal. UserDetails, to provide the necessary information to build an Authentication object from your application's DAO or other source of security data. UserDetailsService, to create a UserDetails when passed in a String-based username (or certificate ID or the like). 6. Core Service AuthenticationManager: just an interface ProvideManager: default implementation for AuthenticationManager, delegate authentication to a list of AuthenticationProviders JdbcDaoImpl: retrieves the user details from a database.

3 7. The Security Filter Chain DelegatingFilterProxy provides the link between web.xml and the application context. 8. Core Security Filters FilterSecurityInterceptor performs security handling of HTTP resources via a filter implementation. The ExceptionTranslationFilter sits above the FilterSecurityInterceptor in the security filter stack. It handles exceptions thrown by the security interceptors and provides suitable and HTTP responses. The AuthenticationEntryPoint will be called if the user requests a secure HTTP resource but they are not authenticated. SecurityContextPersistenceFilter responsible for storage of the SecurityContext contents between HTTP requests and for clearing the SecurityContextHolder when a request is completed. UsernamePasswordAuthenticationFilter processes an authentication form submission. This filter by default responds to the URL /j_spring_security_check. 9. Basic and Digest Authentication BasicAuthenticationFilter is responsible for processing basic authentication credentials presented in HTTP headers. DigestAuthenticationFilter is capable of processing digest authentication credentials presented in HTTP headers. 10. Remember-Me Authentication Remember-me or persistent-login authentication refers to web sites being able to remember the identity of a principal between sessions. This is typically accomplished by sending a cookie to the browser, with the cookie being detected during future sessions and causing automated login to take place. 11. Session Management HTTP session related functionality is handled by a combination of the SessionManagementFilter and the SessionAuthenticationStrategy interface, which the filter delegates to. Typical usage includes session-fixation protection attack prevention, detection of session timeouts and restrictions on how many sessions an authenticated user may have open concurrently.

4 12. Anonymous Authentication 13. Authorization Architecture The GrantedAuthority objects are inserted into the Authentication object by the AuthenticationManager and are later read by AccessDecisionManagers when making authorization decisions. The AccessDecisionManager is called by the AbstractSecurityInterceptor and is responsible for making final access control decisions. Spring Security includes several AccessDecisionManager implementations that are based on voting. RoleHierarchy is used to create a hierarchy of roles. 14. Secure Object Implementations MethodSecurityInterceptor <bean id="bankmanagersecurity" class="org...methodsecurityinterceptor"> <property name="authenticationmanager" ref="authenticationmanager"/> <property name="accessdecisionmanager" ref="accessdecisionmanager"/> <property name="afterinvocationmanager" ref="afterinvocationmanager"/> <property name="securitymetadatasource"> <value> com.mycompany.bankmanager.delete*=role_supervisor com.mycompany.bankmanager.getbalance=role_teller,role_supervisor </value> </property> </bean> 15. Expression-Based Access Control Common Built-in Expressions hasrole([role]) hasanyrole([role1,role2]) principal authentication permitall denyall isanonymous() isrememberme() isauthenticated()

5 decides whether a method can actually be invoked or specifies a method filtering expression which will be evaluated after a method has been invoked. 16. Domain Application Objects (ACL) Spring Security delivers three main ACL-related capabilities to your application: Tables: A way of efficiently retrieving ACL entries for all of your domain objects (and modifying those ACL) A way of ensuring a principal is permitted to work with your objects, before methods are called A way of ensuring a given principal is permitted to work with your objects (or something they return), after methods are called ACL_SID (Security Identity): uniquely identifies a principal or a GrantedAuthority. ACL_CLASS: uniquely identifies any domain object class in the system. ACL_OBJECT_IDENTITY: stores information for each unique domain object instance in the system ACL_ENTRY stores the individual permissions assigned to each recipient 17. Pre-Authentication Scenarios There are situations where you want to use Spring Security for authorization, but the user has already been reliably authenticated by some external system prior to accessing the application. 18. LDAP Authentication LdapAuthenticationProvider: delegates the work to two beans below. LdapAuthenticator: authenticates the user LdapAuthoritiesPopulator: retrieve the user s set of GrantedAuthorities. BindAuthenticator: implements the bind authentication strategy. FilterBasedLdapUserSearch: LdapUserSearch implementation which uses an LDAP filter to locate the user. LdapAuthoritiesPopulator: load a set of authorities for the user

6 19. JSP Tag Libraries <sec:authorize access="hasrole('supervisor')"> <sec:authorize url="/admin"> <sec:authentication property="principal.username" /> <sec:accesscontrollist haspermission="1,2" domainobject="$ {someobject}"> 20. Java Authentication and Authorization Service Provider Spring Security provides a package able to delegate authentication requests to the Java Authentication and Authorization Service (JAAS). 21. CAS Authentication JA-SIG produces an enterprise-wide single sign on system known as CAS. Unlike other initiatives, JA-SIG Central Authentication Service is open source, widely used, simple to understand, platform independent, and supports proxy capabilities. 22. X.509 Authentication Spring Security X.509 module extracts the client certificate using a filter. It maps the certificate to an application user and loads that user's set of granted authorities for use with the standard Spring Security infrastructure. 24. Spring Security Crypto Module The Spring Security Crypto module provides support for symmetric encryption, key generation, and password encoding. B. Main Elements <http> <intercept-url> <form-logging> <concurrency-control> <logout> <authentication-manager> <authentication-provider>