From 0050fbfbec631c91d30ab750a1c279c7fb49f261 Mon Sep 17 00:00:00 2001 From: Arjen Poutsma Date: Wed, 17 Dec 2008 10:47:27 +0000 Subject: [PATCH] typos --- src/docbkx/security.xml | 57 ++++++++++++----------------------------- 1 file changed, 17 insertions(+), 40 deletions(-) diff --git a/src/docbkx/security.xml b/src/docbkx/security.xml index a42b9aaa..7b943d4b 100644 --- a/src/docbkx/security.xml +++ b/src/docbkx/security.xml @@ -41,8 +41,10 @@ - All of these three areas are implemented using theXwsSecurityInterceptor, which we - will describe in. + All of these three areas are implemented using the XwsSecurityInterceptor or + Wss4jSecurityInterceptor, which we + will describe in and + , respectively @@ -57,17 +59,10 @@ XwsSecurityInterceptor - The - XwsSecurityInterceptor - is an - EndpointInterceptor - (see) that is based on SUN's XML and Web Services Security + The XwsSecurityInterceptor is an EndpointInterceptor + (see ) that is based on SUN's XML and Web Services Security package (XWSS). This WS-Security implementation is part of the Java Web Services Developer Pack - ( - - Java WSDP - - ). + (Java WSDP). Like any other endpoint interceptor, it is defined in the endpoint mapping (see @@ -82,26 +77,17 @@ - The - XwsSecurityInterceptor - requires a - security policy file + The XwsSecurityInterceptor requires a security policy file to operate. This XML file tells the interceptor what security aspects to require from incoming SOAP messages, and what aspects to add to outgoing messages. The basic format of the policy file will be explained in the following sections, but you can find a more in-depth tutorial here - - . - You can set the policy with the - policyConfiguration - property, which + . + You can set the policy with the policyConfiguration property, which requires a Spring resource. The policy file can contain multiple elements, e.g. require a username token on incoming messages, and sign all outgoing messages. It contains a - SecurityConfiguration - element as root (not a - JAXRPCSecurity - element). + SecurityConfiguration element as root (not a JAXRPCSecurity element). Additionally, the security interceptor requires one or moreCallbackHandlers to @@ -109,16 +95,11 @@ etc. Spring-WS offers handlers for most common security concerns, e.g. authenticating against a Spring Security authentication manager, signing outgoing messages based on a X509 certificate. The following sections will indicate what callback handler to use for which security concern. You can set the callback - handlers using the - callbackHandler - or - callbackHandlers + handlers using the callbackHandler or callbackHandlers property. - Here is an example that shows how to wire the - XwsSecurityInterceptor - up: + Here is an example that shows how to wire the XwsSecurityInterceptor up: Keystores For most cryptographic operations, you will use the standard - java.security.KeyStore - objects. This includes certificate verification, message signing, signature verification, and encryption, but + java.security.KeyStore objects. + These operations include certificate verification, message signing, signature verification, and encryption, but excludes username and time-stamp verification. This section aims to give you some background knowledge on keystores, and the Java tools that you can use to store keys and certificates in a keystore file. This information is mostly not related to Spring-WS, but to the general cryptographic features of Java. - The - java.security.KeyStore + The java.security.KeyStore class represents a storage facility for cryptographic keys and certificates. It can contain three different sort of elements: @@ -1118,10 +1098,7 @@ Wss4jSecurityInterceptor - The - Wss4jSecurityInterceptor - is an - EndpointInterceptor + The Wss4jSecurityInterceptor is an EndpointInterceptor (see) that is based on Apache's WSS4J.