diff --git a/src/docbkx/namespace-config.xml b/src/docbkx/namespace-config.xml new file mode 100644 index 0000000000..ad9f598752 --- /dev/null +++ b/src/docbkx/namespace-config.xml @@ -0,0 +1,87 @@ + + + + Security Namespace Configuration + +
+ + Introduction + + + Namespace configuration is a feature of Spring 2.0 which allows a bean or beans to be + configured by parsing XML elements from a namespace which are included in your application + context file (in addition to elements from the tradtitional Spring "beans" namespace). You can + find more information in the Spring + + Reference Documentation. A namespace element be used simply to allow a more concise + way of configuring an existing bean or, more powerfully, to define an alternative + configuration syntax which more closely matches the problem domain and hides the underlying + complexity from the user. A relatively simple element may conceal the fact that many beans and + processing steps are being added to the application context. For example, adding the following + element from the securty namespace to an application context will start up an embedded LDAP + server for testing use within the application: + +]]> + which is much simpler than wiring up the equivalent Apache Directory Server beans. The most + common alterative configuration requirements are supported by attributes on the + ldap-server element. + + You can find out more about the use of the + ldap-server + element in the chapter on + LDAP. + . The user is isolated from worrying about which beans they need to be set + on and what the bean property names are. Use of a good XML editor while editing the + configuration file should provide information on the attributes and elements that are + available (and their purpose). + + + To start using the security namespace in your application context, all you need to do is add + the schema declaration to your application context file: + + + ... + + ]]> + In many of the examples you will see (and in the sample) applications, we will often use "security" as the default + namespace rather than "beans", which means we can omit the prefix on all the security namespace elements, + making the context easier to read. You may also want to do this if you have your application context divided up + into separate files and have most of your security configuration in one of them. Your application context file would then + start like this + + ... + +]]> + +
+
+ + Design + + + The namespace is designed to capture the most common uses of the framework and provide a simplified and concise + syntax for enabling them within an application. The design is largely based around the large-scale dependencies + within the framework, and can be divided up into the following areas: + + Web/HTTP Security - the most complex part. Sets up the filters and + related service beans used to apply the framework authentication mechanisms, secure URLs, render login and error pages and much more. + Business Object (Method) Security - options for securing the service layer. + AuthenticationManager - handles authentication requests from other parts of the framework. + AccessDecisionManager - provides access decisions for web and method security. + AuthenticationProviders - mechanisms against which the authentication manager authenticates users. + The namespace provides supports for several standard options and also a means of adding custom beans declared using a traditional syntax. + UserDetailsService - closely related to authentication providers, but often also required by other beans. + + + + +
+ \ No newline at end of file diff --git a/src/docbkx/secured-objects.xml b/src/docbkx/secured-objects.xml index 8e956d3de1..156b2e361f 100644 --- a/src/docbkx/secured-objects.xml +++ b/src/docbkx/secured-objects.xml @@ -1,7 +1,8 @@ -Secure Object Implementations - + + Secure Object Implementations -
AOP Alliance (MethodInvocation) Security Interceptor +
+ AOP Alliance (MethodInvocation) Security Interceptor To secure MethodInvocations, developers diff --git a/src/docbkx/springsecurity.xml b/src/docbkx/springsecurity.xml index 7298b1a2b5..c8a74dfb72 100644 --- a/src/docbkx/springsecurity.xml +++ b/src/docbkx/springsecurity.xml @@ -9,7 +9,7 @@ Reference Documentation - Ben Alex + Ben Alex, Luke Taylor 2.0-SNAPSHOT @@ -80,6 +80,23 @@ Finally, welcome to the Spring Security community. + + + Getting Started + + The remaining parts of this guide provide an in-depth discussion of the + framework architecture and implementation classes, an understanding of which is important + if you need to do any serious customization. In this part, we take a slightly + gentler look at how to get started using some of the features of Spring Security 2.0. + The use of namespace configuration provides a much simpler path to securing + your application with little or no knowledge of the classes involved, unlike the traditional + Spring bean approach which required you to configure large numbers of beans. + + + + + + Overall Architecture @@ -93,15 +110,15 @@ integration. - + - + - + - + - + @@ -117,21 +134,21 @@ - + - + - + - + - + - + - + - +