Spring Security 3.2官方文档详解

5星 · 超过95%的资源需积分: 9 28 浏览量更新于2024-07-25 收藏 1.15MB PDF 举报

"Spring Security官方文档3.2版" Spring Security是一个强大的、高度可定制的身份验证和访问控制框架，用于保护Java应用程序。这份官方文档详细介绍了Spring Security 3.2.0.M2版本的相关内容，包括如何开始使用、新特性、核心组件以及配置方法。在介绍部分，Spring Security被定义为一个全面的安全解决方案，旨在处理身份验证、授权和访问控制。它起源于Acegi Security项目，后来被Spring框架采纳并进一步发展。Spring Security的版本号遵循一定的命名规则，3.2.0.M2表示这是一个预发布版本，意味着它在正式版本发布前的一个中间迭代。文档中提到了Spring Security的核心模块，包括： 1. **spring-security-core.jar**: 提供了核心的安全服务，如访问决策管理器、权限表达式和认证管理。 2. **spring-security-remoting.jar**: 支持远程调用的安全控制。 3. **spring-security-web.jar**: 包含Web应用安全相关的组件，如过滤器链。 4. **spring-security-config.jar**: 提供XML和注解配置支持。 5. **spring-security-ldap.jar**: 对LDAP（轻量级目录访问协议）的支持，实现用户目录认证。 6. **spring-security-acl.jar**: 提供了对象级别的访问控制列表（ACL）功能。 7. **spring-security-cas.jar**: 集成CAS（Central Authentication Service）单点登录协议。 8. **spring-security-openid.jar**: 支持OpenID身份验证协议。 3.1章节详细介绍了Spring Security 3.1版本的新特性，包括高层面的更新和namespace配置的改进。3.2章节则专门讨论了安全namespace配置，这是Spring Security的一个重要组成部分，它允许开发者通过XML配置来声明式地设置安全策略。安全namespace的设计目标是简化和统一安全配置。它提供了一个灵活的框架，用于定义Web应用的安全规则，如定义HTTP安全过滤器链、表单和基本认证方式，以及设定用户登录后的默认跳转页面等。例如，最小化的`<http>`配置可以用于启用基本的安全保护，而更复杂的配置可以添加更多的认证和授权规则。 Spring Security 3.2.0.M2的官方文档为开发者提供了详尽的指南，帮助他们理解和实施这个框架，以保护他们的应用程序免受各种安全威胁。这份文档深入浅出地介绍了Spring Security的核心概念、配置和实践，是学习和使用Spring Security不可或缺的参考资料。

Spring Security

3.2.0.M2 2

1.1 What is Spring Security?

Spring Security provides comprehensive security services for J2EE-based enterprise software applications.

There is a particular emphasis on supporting projects built using The Spring Framework, which is the leading

J2EE solution for enterprise software development. If you're not using Spring for developing enterprise

applications, we warmly encourage you to take a closer look at it. Some familiarity with Spring - and in

particular dependency injection principles - will help you get up to speed with Spring Security more easily.

People use Spring Security for many reasons, but most are drawn to the project after finding the security features

of J2EE's Servlet Specification or EJB Specification lack the depth required for typical enterprise application

scenarios. Whilst mentioning these standards, it's important to recognise that they are not portable at a WAR

or EAR level. Therefore, if you switch server environments, it is typically a lot of work to reconfigure your

application's security in the new target environment. Using Spring Security overcomes these problems, and

also brings you dozens of other useful, customisable security features.

As you probably know two major areas of application security are “authentication” and “authorization” (or

“access-control”). These are the two main areas that Spring Security targets. “Authentication” is the process

of establishing a principal is who they claim to be (a “principal” generally means a user, device or some other

system which can perform an action in your application). “Authorization” refers to the process of deciding

whether a principal is allowed to perform an action within your application. To arrive at the point where an

authorization decision is needed, the identity of the principal has already been established by the authentication

process. These concepts are common, and not at all specific to Spring Security.

At an authentication level, Spring Security supports a wide range of authentication models. Most of these

authentication models are either provided by third parties, or are developed by relevant standards bodies such as

the Internet Engineering Task Force. In addition, Spring Security provides its own set of authentication features.

Specifically, Spring Security currently supports authentication integration with all of these technologies:

• HTTP BASIC authentication headers (an IETF RFC-based standard)

• HTTP Digest authentication headers (an IETF RFC-based standard)

• HTTP X.509 client certificate exchange (an IETF RFC-based standard)

• LDAP (a very common approach to cross-platform authentication needs, especially in large environments)

• Form-based authentication (for simple user interface needs)

• OpenID authentication

• Authentication based on pre-established request headers (such as Computer Associates Siteminder)

• JA-SIG Central Authentication Service (otherwise known as CAS, which is a popular open source single

sign-on system)

• Transparent authentication context propagation for Remote Method Invocation (RMI) and HttpInvoker (a

Spring remoting protocol)

• Automatic "remember-me" authentication (so you can tick a box to avoid re-authentication for a

predetermined period of time)

• Anonymous authentication (allowing every unauthenticated call to automatically assume a particular

security identity)

• Run-as authentication (which is useful if one call should proceed with a different security identity)

• Java Authentication and Authorization Service (JAAS)

Spring Security

3.2.0.M2 3

• JEE container autentication (so you can still use Container Managed Authentication if desired)

• Kerberos

• Java Open Source Single Sign On (JOSSO) *

• OpenNMS Network Management Platform *

• AppFuse *

• AndroMDA *

• Mule ESB *

• Direct Web Request (DWR) *

• Grails *

• Tapestry *

• JTrac *

• Jasypt *

• Roller *

• Elastic Path *

• Atlassian Crowd *

• Your own authentication systems (see below)

(* Denotes provided by a third party

Many independent software vendors (ISVs) adopt Spring Security because of this significant choice of flexible

authentication models. Doing so allows them to quickly integrate their solutions with whatever their end clients

need, without undertaking a lot of engineering or requiring the client to change their environment. If none

of the above authentication mechanisms suit your needs, Spring Security is an open platform and it is quite

simple to write your own authentication mechanism. Many corporate users of Spring Security need to integrate

with "legacy" systems that don't follow any particular security standards, and Spring Security is happy to "play

nicely" with such systems.

Irrespective of the authentication mechanism, Spring Security provides a deep set of authorization capabilities.

There are three main areas of interest - authorizing web requests, authorizing whether methods can be invoked,

and authorizing access to individual domain object instances. To help you understand the differences, consider

the authorization capabilities found in the Servlet Specification web pattern security, EJB Container Managed

Security and file system security respectively. Spring Security provides deep capabilities in all of these

important areas, which we'll explore later in this reference guide.

1.2 History

Spring Security began in late 2003 as “The Acegi Security System for Spring”. A question was posed on

the Spring Developers' mailing list asking whether there had been any consideration given to a Spring-based

security implementation. At the time the Spring community was relatively small (especially compared with the

size today!), and indeed Spring itself had only existed as a SourceForge project from early 2003. The response

to the question was that it was a worthwhile area, although a lack of time currently prevented its exploration.

With that in mind, a simple security implementation was built and not released. A few weeks later another

member of the Spring community inquired about security, and at the time this code was offered to them. Several

other requests followed, and by January 2004 around twenty people were using the code. These pioneering

Spring Security

3.2.0.M2 4

users were joined by others who suggested a SourceForge project was in order, which was duly established

in March 2004.

In those early days, the project didn't have any of its own authentication modules. Container Managed Security

was relied upon for the authentication process, with Acegi Security instead focusing on authorization. This was

suitable at first, but as more and more users requested additional container support, the fundamental limitation

of container-specific authentication realm interfaces became clear. There was also a related issue of adding new

JARs to the container's classpath, which was a common source of end user confusion and misconfiguration.

Acegi Security-specific authentication services were subsequently introduced. Around a year later, Acegi

Security became an official Spring Framework subproject. The 1.0.0 final release was published in May 2006 -

after more than two and a half years of active use in numerous production software projects and many hundreds

of improvements and community contributions.

Acegi Security became an official Spring Portfolio project towards the end of 2007 and was rebranded as

“Spring Security”.

Today Spring Security enjoys a strong and active open source community. There are thousands of messages

about Spring Security on the support forums. There is an active core of developers who work on the code itself

and an active community which also regularly share patches and support their peers.

1.3 Release Numbering

It is useful to understand how Spring Security release numbers work, as it will help you identify the effort

(or lack thereof) involved in migrating to future releases of the project. Each release uses a standard triplet of

integers: MAJOR.MINOR.PATCH. The intent is that MAJOR versions are incompatible, large-scale upgrades

of the API. MINOR versions should largely retain source and binary compatibility with older minor versions,

thought there may be some design changes and incompatible udates. PATCH level should be perfectly

compatible, forwards and backwards, with the possible exception of changes which are to fix bugs and defects.

The extent to which you are affected by changes will depend on how tightly integrated your code is. If you

are doing a lot of customization you are more likely to be affected than if you are using a simple namespace

configuration.

You should always test your application thoroughly before rolling out a new version.

1.4 Getting Spring Security

You can get hold of Spring Security in several ways. You can download a packaged distribution

from the main Spring download page [http://www.springsource.com/download/community?project=Spring

%20Security], download individual jars (and sample WAR files) from the Maven Central repository (or a

SpringSource Maven repository for snapshot and milestone releases) or, alternatively, you can build the project

from source yourself. See the project web site for more details.

Project Modules

In Spring Security 3.0, the codebase has been sub-divided into separate jars which more clearly separate

different functionaltiy areas and third-party dependencies. If you are using Maven to build your project, then

Spring Security

3.2.0.M2 5

these are the modules you will add to your pom.xml. Even if you're not using Maven, we'd recommend that

you consult the pom.xml files to get an idea of third-party dependencies and versions. Alternatively, a good

idea is to examine the libraries that are included in the sample applications.

Core - spring-security-core.jar

Contains core authentication and access-contol classes and interfaces, remoting support and basic provisioning

APIs. Required by any application which uses Spring Security. Supports standalone applications, remote

clients, method (service layer) security and JDBC user provisioning. Contains the top-level packages:

• org.springframework.security.core

• org.springframework.security.access

• org.springframework.security.authentication

• org.springframework.security.provisioning

Remoting - spring-security-remoting.jar

Provides intergration with Spring Remoting. You don't need this unless you are writing a remote client which

uses Spring Remoting. The main package is org.springframework.security.remoting.

Web - spring-security-web.jar

Contains filters and related web-security infrastructure code. Anything with a servlet API dependency. You'll

need it if you require Spring Security web authentication services and URL-based access-control. The main

package is org.springframework.security.web.

Config - spring-security-config.jar

Contains the security namespace parsing code. You need it if you are using the Spring Security XML namespace

for configuration. The main package is org.springframework.security.config. None of the

classes are intended for direct use in an application.

LDAP - spring-security-ldap.jar

LDAP authentication and provisioning code. Required if you need to use LDAP authentication or manage

LDAP user entries. The top-level package is org.springframework.security.ldap.

ACL - spring-security-acl.jar

Specialized domain object ACL implementation. Used to apply security to specific domain object instances

within your application. The top-level package is org.springframework.security.acls.

CAS - spring-security-cas.jar

Spring Security's CAS client integration. If you want to use Spring Security web authentication with a CAS

single sign-on server. The top-level package is org.springframework.security.cas.

剩余182页未读，继续阅读

JoesonChan

粉丝: 3989
资源: 42

Spring Security 3.2官方文档详解

Spring Security 5.1 中文 参考手册 中文文档

spring security 参考手册中文版

Vidi 3.2官方文档（中文）

renren-security开发文档3.2_完整版

renren-security开发文档3.2_完整版.zip

spring security 3.2 帮助文档

springmvc4.1+spring4.1+mybatis3.2+spring-security3.2 jar包

SpringSecurity3.2中文版

Struts2 + Spring 2.5 + Hibernate 3.2 整合文档及事例程序

spring-security-play2:用于 Play Framework 2.3.x 的 Spring Security 3.2.x

最新资源

Spring Security 5.1 中文参考手册中文文档