WebSphere Application Server Network Deployment, Version 6.0.x     Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Web services security troubleshooting tips

Troubleshooting Web services security is best done by reviewing the configurations with assembly tools so that you can match up the client and server request and the response configurations. These configurations must match. A client request sender configuration must match a server request receiver configuration. For encryption to successfully occur, the public key of the receiver must be exported to the sender and this key must be configured properly in the encryption information. For authentication, you must specify the method used by the client in the login mapping of the server. Also, you must correctly specify the actor URI at each point in the configuration with the same URI string. The following includes a list of generic troubleshooting steps that you can perform.

Steps for this task

  1. Verify that the client security extensions and server security extensions match on each downstream call for the following senders and receivers:
    • Request sender and request receiver
    • Response sender and response receiver
  2. Verify that when the Add Created Time Stamp option is enabled on the client-side that the server has the Add Received Time Stamp option configured. You must configure the security extensions with an assembly tool.
  3. Verify that the client security bindings and the server security bindings are correctly configured. When the client authentication method is signature, make sure that the server has a login mapping. When the client uses the public key cn=Bob,o=IBM,c=US to encrypt the body, verify that this Subject is a personal certificate in the server key store so that it can decrypt the body with the private key. You can configure the security bindings using an assembly tool or the WebSphere Application Server administrative console.
  4. Check the SystemOut.log file in the ${USER_INSTALL_ROOT}/logs/server1 directory (server1 changes depending upon the server name) for messages that might provide information about the problem.
  5. Enable trace for Web services security by using the following trace specification: com.ibm.xml.soapsec.*=all=enabled:com.ibm.ws.webservices.*=all=enabled: com.ibm.wsspi.wssecurity.*=all=enabled:com.ibm.ws.security.*=all=enabled: SASRas=all=enabled

    Type the previous three lines as one continuous line.

Errors when securing Web services

"CWWSI5061E: The SOAP Body is not signed" error message displays

Solution:

This error usually occurs whenever the SOAP security handler does not load properly, and does not sign the SOAP body not to be signed. The SOAP security handler is typically the first validation that occurs on the server-side, so a multitude of problems can cause this message to display. The error might be caused by invalid actor URI configurations. You can configure the actor Universal Resource Identifier (URI) at the following locations within the assembly tool:

From the Web services client editor within the assembly tool for client configurations:
  • Click Security Extensions > Client Service Configuration Details and indicate the actor information in the ActorURI field.
  • Click Security Extensions > Request Sender Configuration section > Details and indicate the actor information in the Actor field.
From the Web Services Editor within the assembly tool for server configurations:
  • Click Security Extensions > Server Service Configuration section. Verify that the actor URI has the same actor string as the client-side.
  • Click Security Extensions > Response Sender Service Configuration Details > Details and indicate the actor information in the Actor field.

The actor information on both the client and the server must refer to the same string. When the actor fields on the client and the server match, the request or response is acted upon instead of being forwarded downstream. The actor fields might be different when you have Web services acting as a gateway to other Web services. However, in all other cases, verify that the actor information matches on the client and server. When the Web services implementation is acting as a gateway and it does not have the same actor configured as the request passing through the gateway, this Web services implementation does not process the message from the client. Instead, it sends the request downstream. The downstream process that contains the correct actor string processes the request. The same situation occurs for the response. Therefore, it is important that you verify that the appropriate client and server actor fields are synchronized.

Additionally, the error can appear when you do not specify that the body is signed in the client configuration. To sign the body part of the message using the Web service client editor in the assembly tool, click Security Extensions > Request Sender Configuration > Integrity and select the message parts to sign.

"CWWSI5075E: No security token found that satisfies any one of the authentication methods" error message displays

Verify that the client and server login configuration information matches in the security extensions. Also, verify that the client has a valid login binding and that the server has a valid login mapping in the security bindings. You can check this information by looking at the following locations in the assembly tool:

From the Web services client editor within the assembly tool for client configurations:
  • Click Security Extensions > Request Sender Configuration > Login Configuration verify the authentication method.
  • Click Port Binding > Security Request Sender Binding Configuration > Login Binding verify the authentication method and other parameters.
From the Web Services Editor within the assembly tool for server configurations:
  • Click Security Extensions > Request Receiver Service Configuration Details > Login Configuration and verify the authentication method.
  • Click Binding Configurations > Request Receiver Binding Configuration Details > Login Mapping and verify the authentication method and other parameters.

Also, make sure that the actor URI specified on the client and server matches. You can configure the actor URI at the following locations within the assembly tool:

From the Web services client editor within the assembly tool for client configurations:
  • Click Security Extensions > Client Service Configuration Details and indicate the actor information in the ActorURI field.
  • Click Security Extensions > Request Sender Configuration section > Details and indicate the actor information in the Actor field.
From the Web services editor within the assembly tool for server configurations:
  • Click Security Extensions > Server Service Configuration section. Make sure that the Actor URI field has the same actor string as the client side.
  • Click Security Extensions > Response Sender Service Configuration Details > Details and indicate the actor information in the Actor field.

"CWWSI5094E: No UsernameToken of trusted user was found or the login failed for the user while the TrustMode is BasicAuth" error message displays

Solution:

This situation occurs when you have IDAssertion configured in the login configuration as the authentication method. On the sending Web service, configure a trusted basic authentication entry in the login binding. Then, on the server side, verify that the trusted ID evaluator has a property set that contains the user name of this basic authentication entry. To configure the client for identity assertion, see: To configure the server for identity assertion, see:

"CWSCJ0053E: Authorization failed for /UNAUTHENTICATED..." error message displays

The following authorization error occurs with UNAUTHENTICATED as the security name: CWSCJ0053E: Authorization failed for /UNAUTHENTICATED while invoking (Home)com/ibm/wssvt/tc/pli/ejb/Beneficiary findBeneficiaryBySsNo(java.lang.String):2 securityName: /UNAUTHENTICATED;accessID: null is not granted any of the required roles: AgentRole

This situation occurs because a login configuration is not being configured or Web services Security is not configured from a client to a server. When the request arrives at the server and authentication information is not received, the UNAUTHENTICATED user is set on the thread. Authorization returns this error if there are any roles assigned to the resource except for the special "Everyone" role, which supports access by anyone.

If the client successfully authenticates to an EJB file but the EJB file calls a downstream Enterprise JavaBean (EJB) file that is not configured with Web services security or transport security, such as HTTP user ID and password, an error can occur for this downstream request. Using the assembly tool, verify that the enterprise archive (EAR) file for both client and server has the correct security extensions and security bindings. For more information, see:

"WSWS3243I: Info: Mapping Exception to WebServicesFault." error message is displayed when you specify the value type local name and the URI for a token consumer or the token generator

The Value type URI is not required for the following predefined value type local names:
  • Username token
  • X509 certificate token
  • X509 certificates in a PKIPath
  • A list of X509 certificates and CRLs in a PKCS#7
If you specify one of the previous value type local names, do not enter a value for the Value type URI field.

"Invalid URI: The format of the URI could not be determined" error message might display when you use a Microsoft .NET client that accesses a Web service for WebSphere Application Server

The following exception message might display when you use a Microsoft .NET client that accesses a Web service for WebSphere Application Server. Within WebSphere Application Server, Web services security is enabled and uses the ActorURI attribute.
Invalid URI: The format of the URI could not be determined.
Exception type:
System.UriFormatException 
at System.Uri.Parse() 
at System.Uri..ctor(String uriString, Boolean dontEscape) 
at System.Uri..ctor(String uriString) 
at Microsoft.Web.Services2.SoapInputFilter.CanProcessHeader(XmlElement header, SoapContext context) 
at Microsoft.Web.Services2.Security.SecurityInputFilter.ProcessMessage(SoapEnvelope envelope) 
at Microsoft.Web.Services2.Pipeline.ProcessInputMessage(SoapEnvelope envelope) 
at Microsoft.Web.Services2.InputStream.GetRawContent() 
at Microsoft.Web.Services2.InputStream.get_Length() 
at System.Xml.XmlScanner..ctor(TextReader reader, XmlNameTable ntable) 
at System.Xml.XmlTextReader..ctor(String url, TextReader input, XmlNameTable nt) 
at System.Xml.XmlTextReader..ctor(TextReader input) 
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, 
WebResponse response, Stream responseStream, Boolean asyncCall) 

Solution: This error occurs because Microsoft .Net Web Services Enhancements (WSE) Version 2.0 Service Pack 3 does not support a relative URI value for the ActorURI attribute. WSE Version 2.0 Service Pack 3 supports an absolute Uniform Resource Identifier (URI) for this attribute only. To interoperate with a Microsoft .NET client, you must configure this attribute as an absolute URI. An example of an absolute URI is: abc://myWebService. An example of a relative URI is: myWebService.

To configure ActorURI attribute for use with WebSphere Application Server, use either the Rational Application Developer (RAD) or the Application Server Toolkit (AST) to complete the following steps:
  1. Open the Web Service Editor, click the Extensions tab and expand Server Service Configuration.
  2. Enter the full absolute URI in the Actor field.
  3. Expand Response Generator Service Configuration Details > Details.
  4. Enter the full absolute URI in the Actor field.

"WSEC6664E: Null is not allowed to PKIXBuilderParameters. The configuration of TrustAnchor and CertStoreList are not correct" exception displays

Possible cause:

The certificate path setting is not configured properly.

Possible solution:

Configure the certificate path setting by completing the following steps:
  1. In the administrative console, click Security > Web services.
  2. Under the Default consumer binding heading, click Signing information > configuration_name.
  3. Select either the Trust any or Dedicated signing information option.

    If you select the Dedicated signing information option, select both a trust anchor and a certificate store from the configurations that are provided in the drop-down lists.

  4. Click OK and Save to the master configuration.

"WSE567: The incoming Username token must contain both a nonce and a creation time for the replay detection feature" Microsoft .NET error displays

Scenario:

In this scenario, you have a Web services client for WebSphere Application Server and a Microsoft .NET Web service. The Microsoft .NET Web service has a ws-security constraint for a username token configured. The following exception is thrown from the Microsoft .NET server:

WSE567: The incoming Username token must contain both a nonce and a creation time for the replay detection feature.

Cause:

By default, the Microsoft .NET Web service validates the nonce and the timestamp for the username token. However, it is optional for you to configure the nonce and timestamp properties for a Web service client that is using WebSphere Application Server.

Solution:

Complete the following steps to add the nonce and timestamp properties for a username token on a Web service client for WebSphere Application Server. These steps involve an assembly tool such as Rational Application Developer or the Application Server Toolkit.
  1. Open web service client deployment descriptor and click the WS-Binding tab.
  2. Expand the Security Request Generator Binding Configuration > Token Generator sections.
  3. Click the name of the username token that you already created and click Edit.
  4. In the Properties section of the Token Generator dialog, click Add.
  5. Enter com.ibm.wsspi.wssecurity.token.username.addNonce in the Name field to provide the name of the nonce property.
  6. Enter true in the Value field.
  7. Click Add.
  8. Enter com.ibm.wsspi.wssecurity.token.username.addTimestamp in the Name field to provide the name of the timestamp property.
  9. In the Value field, enter true.
  10. Click OK and save the client deployment descriptor.

For more information about configuring token generators, see Configuring token generators with an assembly tool.




Related tasks
Configuring the client for identity assertion: specifying the method
Configuring the client for identity assertion: collecting the authentication method
Configuring the server to handle identity assertion authentication
Configuring the server to validate identity assertion authentication information
Configuring the client security bindings using an assembly tool
Configuring the security bindings on a server acting as a client using the administrative console
Configuring the server security bindings using an assembly tool
Configuring the server security bindings using the administrative console
Configuring token generators with an assembly tool
Troubleshooting by task
Troubleshooting by component

Related reference
Installation problems

Reference topic    

Terms of Use | Feedback

Last updated: Dec 11, 2005 4:07:15 PM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/rwbs_troubleshoot.html

© Copyright IBM Corporation 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)