Document

TIBCO BusinessWorks: Understanding Web Services Security 24

Go to Show Console and look at the stack trace. It is interesting and informative to see all the WSS headers in
place, but if you scroll down to the bottom, you will see a WS Security Error:
<Data>
<defaultFaultElement>
<faultcode>SOAP-ENV:Server</faultcode>
<faultstring>WS Security Error : 131901</faultstring>
<faultactor/>
</defaultFaultElement>
</Data>

6.1.3 Troubleshooting Administrator is unavailable
Stop the Administrator, retest and you wont find any difference as Designer is doing some caching, so completely
stop and restart Designer and test again.
You will get the same error - SOAPPLUGIN100023, but the Fault will be different WS Security Error: 111000.
<Data>
<defaultFaultElement>
<faultcode>SOAP-ENV:Server</faultcode>
<faultstring>WS Security Error : 111000</faultstring>
<faultactor/>
</defaultFaultElement>
</Data>

6.1.4 Troubleshooting Mismatched Configurations
Lets set it up so that the Client DOESNT send any Authentication Data and the Server expects it. Change the
Outbound Policy by un-checking the Authentication box.
Document
TIBCO BusinessWorks: Understanding Web Services Security 25
Here is what we get:
<Data>
<defaultFaultElement>
<faultcode>SOAP-ENV:Server</faultcode>
<faultstring>WS Security Error : 181001</faultstring>
<faultactor/>
</defaultFaultElement>
</Data>

The opposite mismatch doesnt result in any errors as the Client is sending Authentication data, but the Server isnt
checking for it.
7 Change Project from UserName to X.509 for Identification
Modify both the Inbound and Outbound Policies as follows:
Inbound Policy:
Authentication Tab - Highlight X509Token and pick the Trusted Certificates Folder as shown below:

Outbound Policy:
Authentication Tab pick X509Token as the Security Token, and pick the Identity we created as shown below: