English | 简体中文 | 繁體中文 | Русский язык | Français | Español | Português | Deutsch | 日本語 | 한국어 | Italiano | بالعربية
In Spring Security 3In version 0.0, the "Security" module is divided into separate jar files. The purpose is to divide according to the functionality of the jar files, so that developers can integrate according to their requirements.
This also helps to set the required dependencies in the pom.xml file of the Maven project.
The following are the jar files included in the Spring Security module.
spring-security-core.jar spring-security-remoting.jar spring-security-web.jar spring-security-config.jar spring-security-ldap.jar spring-security-oauth2-core.jar spring-security-oauth2-client.jar spring-security-oauth2-jose.jar spring-security-acl.jar spring-security-cas.jar spring-security-openid.jar spring-security-test.jar
This is the core jar file, which is essential for each application that wants to use Spring Security. This jar file contains core access control and core authentication classes and interfaces. We can use it in standalone applications or remote client applications.
It includes the top-level package:
org.springframework.security.core org.springframework.security.access org.springframework.security.authentication org.springframework.security.provisioning
This jar is used to integrate security features into Spring remote applications. We only need it until or unless a remote application is created. All classes and interfaces are located in org.springframework.security.remoting in the package.
This jar is very useful for Spring Security Web authentication and URL-based access control. It includes filters and Web security infrastructure.
All classes and interfaces are located in org.springframework.security.web in the package.
This jar file is essential for configuring Spring Security using both XML and Java. It includes Java configuration code and security namespace parsing code. All classes and interfaces are stored in org.springframework.security.config in the package.
This jar file is needed only when we are using LDAP (Lightweight Directory Access Protocol). It includes authentication and configuration code. All classes and interfaces are stored in org.springframework.security.ldap in the package.
This jar is required to use Oauth 2.0 authorization framework and OpenID Connect Core 1.0 integrated into the application. This jar file contains OAuth 2.0 core classes, and these classes are stored in org.springframework.security.oauth2.core in the package.
This jar file is necessary to obtain OAuth 2.0 authorization framework and OpenID Connect Core 1is required for client support of version .0. This module provides OAuth login and OpenID client support. All classes and interfaces can be found from org.springframework.security.oauth2.client can be obtained from the package.
It provides support for Spring Security within the JOSE (Javascript Object Signing and Encryption) framework. The JOSE framework provides methods for establishing secure connections between clients. It includes the following set of specifications:
JWT (JSON Web Token) JWS (JSON Web Signature) JWE (JSON Web Encryption) JWK(JSON Web Key)
All classes and interfaces are available in both packages:
org.springframework.security.oauth2.jwt and org.springframework.security.oauth2.jose.
This jar is used to apply security to domain objects in the application. We can get from org.springframework.security.acls package to access classes and code.
Spring Security CAS client integration is required. We can use it to integrate Spring Security Web authentication with CAS single sign-on server. Source code is located at org.springframework.security.cas in the package.
This jar is used for OpenID Web authentication support. We can use it to authenticate users against external OpenID servers. It requires the use of OpenID4Java, top-level package for org.springframework.security.openid .
This jar provides support for testing the Spring Security application.