+

Search Tips   |   Advanced Search

 

ws-security.xml file - Default configuration for WebSphere Application Server ND

 

WAS ND installation uses the ws-security.xml file to define the default binding information for Web services security for an entire cell.

There is an important distinction between V5.x and V6 and later applications. The information in this article supports V5.x applications only that are used with WebSphere Application Server V6.0.x and later. The information does not apply to V6.0.x and later applications. In the WebSphere Application Server ND installation, the ws-security.xml file is at the cell level and defines the default binding information for Web services security for the entire cell. But each appserver can have its own ws-security.xml file to override the cell default; similarly, each Web service can override the default in its binding files. The following list contains the defaults defined in ws-security.xml file:

Trust anchors

Identifies the trusted root certificates for signature verification.

Collection certificate stores

Contains certificate revocation lists (CRLs) and nontrusted certificates for verification.

Key locators

Locates the keys for digital signature and encryption.

Trusted ID evaluators

Evaluates the trust of the received identity before identity assertion.

Login mappings

Contains the JAAS configurations for AuthMethod token validation.

The Web services security run time reads the configuration from the application bindings first, then tries the server-level, and finally tries the cell level. The following figure depicts the run-time configuration process. Figure 1. Run-time configuration




 

Related concepts


Default binding
Trust anchors
Collection certificate store
Key locator
Trusted ID evaluator
Login mappings

 

Related tasks


Securing Web services for V5.x applications using XML digital signature

 

Reference topic