Sun logo      Previous      Contents      Next     

Sun Java System Application Server Enterprise Edition 8.1 Administration Guide 2005Q1

Chapter 15
Configuring Message
Security

This chapter describes the configuration of message layer security for web services in the Sun Java System Application Server 8.1 2005Q1. This chapter contains the following topics:

Some of the material in this chapter assumes a basic understanding of security and web services concepts. To learn more about these concepts, explore the resources listed in "Further Information" before beginning this chapter.

About Message Security

Overview of Message Security

In message security, security information is inserted into messages so that it travels through the networking layers and arrives with the message at the message destination(s). Message security differs from transport layer security (which is discussed in the Security chapter of the J2EE 1.4 Tutorial) in that message security can be used to decouple message protection from message transport so that messages remain protected after transmission.

Web Services Security: SOAP Message Security (WS-Security) is an international standard for interoperable Web Services Security that was collaboratively developed in OASIS by all the major providers of web services technology (including Sun Microsystems). WS-Security is a message security mechanism that uses XML Encryption and XML Digital Signature to secure web services messages sent over SOAP. The WS-Security specification defines the use of various security tokens including X.509 certificates, SAML assertions, and username/password tokens to authenticate and encrypt SOAP web services messages.

The WS-Security specification can be viewed at the following URL:

http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0 .pdf

Understanding Message Security in the Application Server

The Sun Java System Application Server 8.1 2005Q1 offers integrated support for the WS-Security standard in its web services client and server-side containers. This functionality is integrated such that web services security is enforced by the containers of the Application Server on behalf of applications, and such that it can be applied to protect any web service application without requiring changes to the implementation of the application. The Application Server achieves this effect by providing facilities to bind SOAP layer message security providers and message protection policies to containers and to applications deployed in containers.

Assigning Message Security Responsibilities

In Sun Java System Application Server 8.1 2005Q1, the System Administrator and Application Deployer roles are expected to take primary responsibility for configuring message security. In some situations, the Application Developer may also contribute, although in the typical case either of the other roles may secure an existing application without changing its implementation without involving the developer. The responsibilities of the various roles are defined in the following sections:

System Administrator

The system administrator is responsible for:

A system administrator uses the Admin Console to manage server security settings and uses a command line tool to manage certificate databases. In PE, certificates and private keys are stored in keystores and are managed with keytool. SE and EE store certificates and private keys in an NSS database, where they are managed using certutil. This document is intended primarily for system administrators. For an overview of message security tasks, see "Configuring the Application Server for Message Security".

Application Deployer

The application deployer is responsible for:

These security tasks are discussed in the Securing Applications chapter of the Developers’ Guide. For a link to this chapter, see "Further Information".

Application Developer

The application developer can turn on message security, but is not responsible for doing so. Message security can be set up by the System Administrator so that all web services are secured, or by the Application Deployer when the provider or protection policy bound to the application must be different from that bound to the container.

The application developer or assembler is responsible for the following:

About Security Tokens and Security Mechanisms

The WS-Security specification provides an extensible mechanism for using security tokens to authenticate and encrypt SOAP web services messages. The SOAP layer message security providers installed with the Application Server may be used to employ username/password and X509 certificate security tokens to authenticate and encrypt SOAP web services messages. Additional providers that employ other security tokens including SAML assertions will be installed with subsequent releases of the Application Server.

About Username Tokens

The Application Server uses Username tokens in SOAP messages to establish the authentication identity of the message sender. The recipient of a message containing a Username token (within embedded password) validates that the message sender is authorized to act as the user (identified in the token) by confirming that the sender knows the secret (i.e. the password) of the user.

When using a Username token, a valid user database must be configured on the Application Server. For more information on this topic, read "Editing a Realm".

About Digital Signatures

The Application Server uses XML Digital signatures to bind an authentication identity to message content. Clients use digital signatures to establish their caller identity, analogous to the way basic authentication or SSL client certificate authentication have been used to do the same thing when transport layer security is being used. Digital signatures are verified by the message receiver to authenticate the source of the message content (which may be different from the sender of the message.)

When using digital signatures, valid keystore and truststore files must be configured on the Application Server. For more information on this topic, read "About Certificate Files".

About Encryption

The purpose of encryption is to modify the data such that it can only be understood by its intended audience. This is accomplished by substituting an encrypted element for the original content. When predicated on public key cryptography, encryption can be used to establish the identity of the parties that can read a message.

When using Encryption, you must have an installed JCE provider that supports encryption. For more information on this topic, read "Configuring a JCE Provider".

About Message Protection Policies

Message protection policies are defined for request message processing and response message processing and are expressed in terms of requirements for source and/or recipient authentication. A source authentication policy represents a requirement that the identity of the entity that sent a message or that defined the content of a message be established in the message such that it can be authenticated by the message receiver. A recipient authentication policy represents a requirement that the message be sent such that the identity of the entity(s) that can receive the message can be established by the message sender. The providers apply specific message security mechanisms to cause the message protection policies to be realized in the context of SOAP web services messages.

Request and response message protection policies are defined when a provider is configured into a container. Application-specific message protection policies (at the granularity of the web service port or operation) may also be configured within the Sun-specific deployment descriptors of the application or application client. In any case, where message protection policies are defined, the request and response message protection policies of the client must match (i.e. be equivalent to) the request and response message protection policies of the server. For more information on defining application-specific message protection policies, refer to the Securing Applications chapter of the Developers’ Guide. There is a link to this chapter in "Further Information".

Glossary of Message Security Terminology

The terminology used in this document is described below. The concepts are also discussed in "Configuring the Application Server for Message Security".

Securing a Web Service

Web services deployed on the Application Server are secured by binding SOAP layer message security providers and message protection policies to the containers in which the applications are deployed or to web service endpoints served by the applications. SOAP layer message security functionality is configured in the client-side containers of the Application Server by binding SOAP layer message security providers and message protection policies to the client containers or to the portable service references declared by client applications.

When the Application Server is installed, SOAP layer message security providers are configured in the client and server-side containers of the Application Server, where they are available for binding for use by the containers, or by individual applications or clients deployed in the containers. During installation, the providers are configured with a simple message protection policy that, if bound to a container, or to an application or client in a container, would cause the source of the content in all request and response messages to be authenticated by XML digital signature.

The administrative interfaces of the Application Server can be employed to bind the existing providers for use by the server-side containers of the Application Server, to modify the message protection policies enforced by the providers, or to create new provider configurations with alternative message protection policies. These operations are defined in "Admin Console Tasks for Message Security". Analogous administrative operations can be performed on the SOAP message layer security configuration of the application client container as defined in Enabling Message Security for Client Applications.

By default, message layer security is disabled on the Application Server. To configure message layer security for the Application Server follow the steps outlined in "Configuring the Application Server for Message Security". If you want to cause web services security to be used to protect all web services applications deployed on the Application Server, follow the steps in "Enabling Providers for Message Security" and "Enabling Message Security for Client Applications".

Once you have completed the above steps (which may include restarting the Application Server), web services security will be applied to all web services applications deployed on the Application Server.

Configuring Application-Specific Web Services Security

Application-specific web services security functionality is configured (at application assembly) by defining message-security-binding elements in the Sun-specific deployment descriptors of the application. These message-security-binding elements are used to associate a specific provider or message protection policy with a web services endpoint or service reference, and may be qualified so that they apply to a specific port or method of the corresponding endpoint or referenced service.

For more information on defining application specific message protection policies, refer to the Securing Applications chapter of the Developers’ Guide. There is a link to this chapter in "Further Information".

Securing the Sample Application

The Application Server ships with a sample application named xms. The xms application features a simple web service that is implemented by both a J2EE EJB endpoint and a Java Servlet endpoint. Both endpoints share the same service endpoint interface. The service endpoint interface defines a single operation, sayHello, which takes a string argument, and returns a String composed by prepending Hello to the invocation argument.

The xms sample application is provided to demonstrate the use of the Application Server’s WS-Security functionality to secure an existing web services application. The instructions which accompany the sample describe how to enable the WS-Security functionality of the Application Server such that it is used to secure the xms application. The sample also demonstrates the binding of WS-Security functionality directly to the application (as described in Configuring Application-Specific Web Services Security) such that it applies specifically to the application.

The xms sample application is installed in the directory: install_dir\samples\webservices\security\ejb\apps\xms\

For information on compiling, packaging, and running the xms sample application, refer to the Securing Applications chapter of the Developers’ Guide. There is a link to this chapter in "Further Information".

Configuring the Application Server for Message Security

The Application Server implements message security using message security providers integrated in its SOAP processing layer. The message security providers depend on other security facilities of Application Server.

To configure these other facilities follow these steps:

  1. If using a version of the Java SDK prior to version 1.5.0, and using encryption technology, configure a JCE provider.

    2. Configuring a JCE provider is discussed in "Configuring a JCE Provider".

  2. If using a username token, configure a user database, if necessary. When using a username/password token, an appropriate realm must be configured and an appropriate user database must be configured for the realm.

    3. Configuring a user database is discussed in "Editing a Realm".

  3. Manage certificates and private keys, if necessary.

    4. Managing certificates and private keys is discussed in "About Certificate Files".

Once the facilities of the Application Server are configured for use by message security providers, then the providers installed with the Application Server may be enabled as described in Enabling Providers for Message Security.

Configuring a JCE Provider

The Java Cryptography Extension (JCE) provider included with J2SE 1.4.x does not support RSA encryption. Because the XML Encryption defined by WS-Security is typically based on RSA encryption, in order to use WS-Security to encrypt SOAP messages you must download and install a JCE provider that supports RSA encryption.

Note: RSA is public-key encryption technology developed by RSA Data Security, Inc. The acronym stands for Rivest, Shamir, and Adelman, the inventors of the technology.

If you are running the Application Server on version 1.5 of the Java SDK, the JCE provider is already configured properly. If you are running the Application Server on version 1.4.x of the Java SDK, follow these steps to add a JCE provider statically as part of your JDK environment:

  1. Download and install a JCE provider JAR (Java ARchive) file. The following URL provides a list of JCE providers that support RSA encryption:
  1. Copy the JCE provider JAR file to <JAVA_HOME>/jre/lib/ext/.
  2. Stop the Application Server. If the Application Server is not stopped and then restarted later in this process, the JCE provider will not be recognized by the Application Server.
  3. Edit the <JAVA_HOME>/jre/lib/security/java.security properties file in any text editor. Add the JCE provider you’ve just downloaded to this file. The java.security file contains detailed instructions for adding this provider. Basically, you need to add a line of the following format in a location with similar properties:
    4. security.provider.<n>=<provider class name>
  1. Save and close the file.
  2. Restart the Application Server.

Admin Console Tasks for Message Security

Most of the steps for setting up the Application Server for using message security can be accomplished using the Admin Console, the asadmin command-line tool, or by manually editing system files. In general, editing system files is discouraged due to the possibility of making unintended changes that prevent the Application Server from running properly, therefore, where possible, steps for configuring the Application Server using the Admin Console are shown first, with the asadmin tool command shown after. Steps for manually editing system files are shown only when there is no Admin Console or asadmin equivalent.

Support for message layer security is integrated into the Application Server and its client containers in the form of (pluggable) authentication modules. By default, message layer security is disabled on the Application Server. The following sections provide the details for enabling, creating, editing, and deleting message security configurations and providers.

In most cases, it will be necessary to restart the Application Server after performing the administrative operations listed above. This is especially the case if you want the effects of the administrative change to be applied to applications that were already deployed on the Application Server at the time the operation was performed.

Enabling Providers for Message Security

To enable message security for web services endpoints deployed in the Application Server, you must specify a provider to be used by default on the server side. If you enable a default provider for message security, you also need to enable providers to be used by clients of the web services deployed in the Application Server. Information for enabling the providers used by clients is discussed in "Enabling Message Security for Client Applications".

To enable message security for web service invocations originating from deployed endpoints, you must specify a default client provider. If you enabled a default client provider for the Application Server, you must ensure that any services invoked from endpoints deployed in the Application Server are compatibly configured for message layer security.

To enable the default providers for the Application Server, follow these steps.

  1. In the Admin Console tree component, expand the Configurations node.
  2. Select the instance to configure:
    1. To configure a particular instance, select the instance’s config node. For example, the default instance, server, select the server-config node.
    2. To configure the default settings for all instances, select the default-config node.
  3. Expand the Security node.
  4. Expand the Message Security node.
  5. Select the SOAP node.
  6. Select the Message Security tab.
  7. On the Edit Message Security Configuration page, specify a provider to be used on the server side and a provider to be used on the client side for all applications for which a specific provider has not been bound. This is accomplished by modifying the following optional properties:
    • Default Provider – The identity of the server provider to be invoked for any application for which a specific server provider has not been bound.

      By default, no provider configuration is selected for the Application Server. To identify a server-side provider, select ServerProvider. Selecting the null option means that no message security provider will be invoked (by default) on the server side.

      You would generally select ServerProvider for this field.

    • Default Client Provider – The identity of the client provider to be invoked for any application for which a specific client provider has not been bound.

      • By default, no provider configuration is selected for the Application Server. To identify a client-side provider, select ClientProvider. Selecting the null option means that no message security provider will be invoked (by default) on the client side.

      You would generally select null for this field. You would select ClientProvider if you wanted to enable a default provider and message protection policy to apply to the web services invocations originating from web services endpoints deployed on the Application Server.

  8. Click Save.
  9. If you enabled a client or server provider, and you want to modify the message protection policies of the enabled providers, then refer to "Configuring a Message Security Provider" for information on modifying the configuration of the message security providers enabled in this step.

Equivalent asadmin commands:

Configuring a Message Security Provider

Typically, a provider would be reconfigured to modify its message protection policies, although the provider type, implementation class, and provider-specific configuration properties may also be modified. Follow the steps listed below to reconfigure a message security provider.

  1. In the Admin Console tree component, expand the Configurations node.
  2. Select the instance to configure:
    1. To configure a particular instance, select the instance’s config node. For example, the default instance, server, select the server-config node.
    2. To configure the default settings for all instances, select the default-config node.
  3. Expand the Security node.
  4. Expand the Message Security node.
  5. Select the SOAP node.
  6. Select the Providers tab.
  7. Select the message security provider to edit. ClientProvider and ServerProvider ship with the Application Server.
  8. In the Provider Config section of the Edit Provider Config page, the following properties are available for modification:
    • Provider Type – Select client, server, or client-server to establish whether the provider is to be used as a client authentication provider, a server authentication provider, or both (a client-server provider).
    • Class Name - Enter the Java implementation class of the provider. Client authentication providers must implement the com.sun.xml.wss.provider.ClientSecurityAuthModule interface. Server-side providers must implement the com.sun.xml.wss.provider.ServerSecurityAuthModule interface. A provider may implement both interfaces, but it must implement the interface corresponding to its provider type.
  9. In the Request Policy section of the Create a Provider Configuration page, enter the following optional values, if needed. These properties are optional, but if not specified, no authentication is applied to request messages.
  1. In the Response Policy section of the Create a Provider Configuration page, enter the following optional properties, if needed. These properties are optional, but if not specified, no authentication is applied to response messages.
  1. Add additional properties by clicking the Add Property button. The provider that is shipped with the Application Server supports the property listed below. If other providers are used, refer to their documentation for more information on properties and valid values.
    • server.config - The directory and file name of an XML file that contains the server configuration information. For example, install_dir/domains/domain_dir/config/wss-server-config.xml.
  2. Click Save.

Equivalent asadmin commands are listed below. To set the response policy, replace the word request in the following commands with response.

Creating a Message Security Provider

To create a new message security provider, follow these steps. To configure an existing provider, follow the steps in "Configuring a Message Security Provider".

  1. In the Admin Console tree component, expand the Configurations node.
  2. Select the instance to configure:
    1. To configure a particular instance, select the instance’s config node. For example, the default instance, server, select the server-config node.
    2. To configure the default settings for all instances, select the default-config node.
  3. Expand the Security node.
  4. Expand the Message Security node.
  5. Select the SOAP node.
  6. Select the Providers tab.
  7. On the Provider Configuration page, click New.
  8. In the Provider Config section of the Create a Provider Configuration page, enter the following:
    • Default Provider – Check the box beside this field to make the new message security provider the provider to be invoked for any application for which a specific provider has not been bound. Whether the provider becomes the default client provider, the default server provider, or both will be based on the value selected for Provider Type.
    • Provider Type – Select client, server, or client-server to establish whether the provider is to be used as a client authentication provider, a server authentication provider, or both (a client-server provider).
    • Provider ID - Enter an identifier for this provider configuration. This name will appear in the Current Provider Configurations list.
    • Class Name - Enter the Java implementation class of the provider. Client authentication providers must implement the com.sun.xml.wss.provider.ClientSecurityAuthModule interface. Server-side providers must implement the com.sun.xml.wss.provider.ServerSecurityAuthModule interface. A provider may implement both interfaces, but it must implement the interface corresponding to its provider type.
  9. In the Request Policy section of the Create a Provider Configuration page, enter the following optional values, if needed. These properties are optional, but if not specified, no authentication is applied to request messages.
    • Authentication Source – Select sender, content, or null (the blank option) to define a requirement for message-layer sender authentication (for example, username password), content authentication (for example, digital signature), or no authentication be applied to request messages. When null is specified, source authentication of the request is not required.
    • Authentication Recipient – Select beforeContent or afterContent to define a requirement for message-layer authentication of the receiver of the request message to its sender (e.g. by XML encryption). When the value is not specified it defaults to afterContent.

      • For a description of the actions performed by the SOAP message security providers as a result of the following message protection policies see "Actions of Request and Response Policy Configurations".

  10. In the Response Policy section of the Create a Provider Configuration page, enter the following optional properties, if needed. These properties are optional, but if not specified, no authentication is applied to response messages.
    • Authentication Source – Select sender, content, or null (the blank option) to define a requirement for message-layer sender authentication (for example, username password) or content authentication (for example, digital signature) to be applied to response messages. When null is specified, source authentication of the response is not required.
    • Authentication Recipient – Select beforeContent or afterContent to define a requirement for message-layer authentication of the receiver of the response message to its sender (e.g. by XML encryption). When the value is not specified it defaults to afterContent.

      • For a description of the actions performed by the SOAP message security providers as a result of the following message protection policies see "Actions of Request and Response Policy Configurations".

  11. Add additional properties by clicking the Add Property button. The provider that is shipped with the Application Server supports the property listed below. If other providers are used, refer to their documentation for more information on properties and valid values.
    • server.config - The directory and file name of an XML file that contains the server configuration information. For example, install_dir/domains/domain_dir/config/wss-server-config.xml.
  12. Click OK to save this configuration, or click Cancel to quit without saving.

Equivalent asadmin command: create-message-security-provider

Actions of Request and Response Policy Configurations

Table 15-1 shows message protection policy configurations and the resulting message security operations performed by the WS-Security SOAP message security providers for that configuration.

Table 15-1  Message protection policy to WS-Security SOAP message security operation mapping

Message Protection Policy

Resulting WS-Security SOAP message protection operations

auth-source="sender"

The message contains a wsse:Security header that contains a wsse:UsernameToken (with password).

auth-source="content"

The content of the SOAP message Body is signed. The message contains a wsse:Security header that contains the message Body signature represented as a ds:Signature.

auth-source=”sender”

auth-recipient="before-content"

OR

auth-recipient="after-content"

The content of the SOAP message Body is encrypted and replaced with the resulting xend:EncryptedData. The message contains a wsse:Security header that contains a wsse:UsernameToken (with password) and an xenc:EncryptedKey. The xenc:EncryptedKey contains the key used to encrypt the SOAP message body. The key is encrypted in the public key of the recipient.

auth-source="content"

auth-recipient="before-content"

The content of the SOAP message Body is encrypted and replaced with the resulting xend:EncryptedData. The xenc:EncryptedData is signed. The message contains a wsse:Security header that contains an xenc:EncryptedKey and a ds:Signature. The xenc:EncryptedKey contains the key used to encrypt the SOAP message body. The key is encrypted in the public key of the recipient.

auth-source="content"

auth-recipient="after-content"

The content of the SOAP message Body is signed, then encrypted, and then replaced with the resulting xend:EncryptedData. The message contains a wsse:Security header that contains an xenc:EncryptedKey and a ds:Signature. The xenc:EncryptedKey contains the key used to encrypt the SOAP message body. The key is encrypted in the public key of the recipient.

auth-recipient="before-content"

OR

auth-recipient="after-content"

The content of the SOAP message Body is encrypted and replaced with the resulting xend:EncryptedData. The message contains a wsse:Security header that contains an xenc:EncryptedKey. The xenc:EncryptedKey contains the key used to encrypt the SOAP message body. The key is encrypted in the public key of the recipient.

No policy specified.

No security operations are performed by the modules.

Deleting a Message Security Configuration

To delete a message security configuration, follow these steps.

  1. In the Admin Console tree component, expand the Configurations node.
  2. Select the instance to configure:
    1. To configure a particular instance, select the instance’s config node. For example, the default instance, server, select the server-config node.
    2. To configure the default settings for all instances, select the default-config node.
  3. Expand the Security node.
  4. Select the Message Security node.
  5. Click in the checkbox to the left of the Message Security Configuration to be deleted.
  6. Click Delete.

Deleting a Message Security Provider

To delete a message security provider, follow these steps.

  1. In the Admin Console tree component, expand the Configurations node.
  2. Select the instance to configure:
    1. To configure a particular instance, select the instance’s config node. For example, the default instance, server, select the server-config node.
    2. To configure the default settings for all instances, select the default-config node.
  3. Expand the Security node.
  4. Expand the Message Security node.
  5. Select the SOAP node.
  6. Select the Providers page.
  7. Click in the checkbox to the left of the Provider Configuration to be deleted.
  8. Click Delete.

Equivalent asadmin command: delete-message-security-provider

Enabling Message Security for Client Applications

The message protection policies of client providers must be configured such that they are equivalent to the message protection policies of the server-side providers they will be interacting with. This is already the case for the providers configured (but not enabled) when the Application Server is installed.

To enable message security for client applications, modify the Sun Java System Application Server-specific configuration for the application client container.

To enable a default client provider in the application client, follow these steps:

  1. Stop any client applications that depend on the client container descriptor.
  2. In a text editor, open the Sun application client container descriptor, located in install_dir/domains/domain_dir/config/sun-acc.xml.
  3. Add the text in bold to the file to enable the default client provider in the application client. The other code is provided to show where the code to enable message security for client applications should be located. The code that is not in bold may differ slightly in your installation, do not change the text that is not in bold.
    4. <client-container>
      <target-server name="<your_host>" address="<your_host>" port="<your_port>"/>
      <log-service file="" level="WARNING"/>
      <message-security-config auth-layer="SOAP"     default-client-provider="ClientProvider">
        <provider-config
          class-name="com.sun.xml.wss.provider.ClientSecurityAuthModule"       provider-id="ClientProvider" provider-type="client">
          <request-policy auth-source="sender"/>
          <response-policy/>
           <property name="security.config"       value="C:/Sun/AppServer/lib/appclient/wss-client-config.xml"/>
        </provider-config>
      </message-security-config>
    </client-container>

The message security provider configured in the client container will also require access to private keys and trusted certificates. This is accomplished by defining appropriate values for the following system properties in the application client startup script.

Setting the Request and Response Policy for the Application Client Configuration

The request and response policies define the authentication policy requirements associated with request and response processing performed by the authentication provider. Policies are expressed in message sender order such that a requirement that encryption occur after content would mean that the message receiver would expect to decrypt the message before validating the signature.

To achieve message security, the request and response policies must be enabled on both the server and client. When configuring the policies on the client and server, make sure that the client policy matches the server policy for request/response protection at application-level message binding.

To set the request policy for the application client configuration, modify the Sun Java System Application Server-specific configuration for the application client container as described in "Enabling Message Security for Client Applications". In the application client configuration file, add the text in bold to set the request policy. The other code is provided for reference. The code that is not in bold may differ slightly in your installation, do not change the text that is not in bold.

<client-container>
  <target-server name="<your_host>" address="<your_host>" port="<your_port>"/>
  <log-service file="" level="WARNING"/>
  <message-security-config auth-layer="SOAP"     default-client-provider="ClientProvider">
    <provider-config
      class-name="com.sun.xml.wss.provider.ClientSecurityAuthModule"       provider-id="ClientProvider" provider-type="client">
      <request-policy auth-source="sender | content"
        auth-recipient=”after-content | before-content”/>
      <response-policy auth-source="sender | content"
        auth-recipient=”after-content | before-content”/>
       <property name="security.config"       value="install_dir/lib/appclient/wss-client-config.xml"/>
    </provider-config>
  </message-security-config>
</client-container>

Valid values for auth-source include sender and content. Valid values for auth-recipient include before-content and after-content. A table describing the results of various combinations of these values can be found in "Actions of Request and Response Policy Configurations".

To not specify a request or response policy, leave the element blank, for example,

      <response-policy/>

Further Information



Previous      Contents      Next     

Copyright 2004 - 2005 Sun Microsystems, Inc. All rights reserved.