Release Notes › Known Issues › SOA Security Gateway Issues › SOA Security Gateway Sign Message Filter Fails to Sign SOAP Messages on Solaris

SOA Security Gateway Sign Message Filter Fails to Sign SOAP Messages on Solaris

When a SOA Security Gateway on Solaris is configured to sign a SOAP message body with a valid Certificate (Signing Key) using the Sign Message filter, it fails to sign the SOAP message and the following error is written to the trace log:

ERROR   18:56:32:934 [023d]     signature error: not specified/not specified, key is not found:   (source location xmldsig.c/900)
ERROR   18:56:32:935 [023d]     signature error: xmlSecDSigCtxProcessKeyInfoNode/not specified, xmlsec library function failed:   (source location xmldsig.c/569)
ERROR   18:56:32:935 [023d]     signature error: xmlSecDSigCtxSigantureProcessNode/not specified, xmlsec library function failed:   (source location xmldsig.c/306)
ERROR   18:56:32:936 [023d] Filter that caused failure: Sign Message
ERROR   18:56:32:936 [023d] Policy 'some {
ERROR   18:56:32:936 [023d]     Filter 'Sign Message' Status:  ABORTED
ERROR   18:56:32:936 [023d] }
…

This problem is caused by broken symbolic links in SOA_HOME/SOASecurityGateway/platform/lib.

Workaround

A script that fixes the broken symbolic links is included in the SOA Security Manager r12.1 CR1 distribution. To fix the broken symbolic links, perform the following steps:

1. Copy the GatewayLinks script from the top directory of the SOA Security Manager r12.1 CR1 distribution to the following location:

   SOA_HOME/SOASecurityGateway/platform/lib
   

2. In a command window, navigate to the SOA_HOME/SOASecurityGateway/platform/lib directory.
3. Verify that the GatewayLinks script is executable by typing the following command:

   chmod +x GatewayLinks
   

4.  Run the GatewayLinks script by typing the following command:

   ./GatewayLinks
   

5.  Restart the SOA Security Gateway.