"useSingleClientIdentification" tells whether it is desirable for any Web Service use the same client X.509 certificate. When the decision is to enable this filter then all the SALT client request will use the identity configured in "defaultClientIdentification", if "defaultCleintIdentification" is not configured then it is a configuration error and "wsloadcf" will issue an error. By default it is disabled.

This filter only affects the runtime client X.509 certificate selection when Tuxedo "SECURITY" is configured at least at "USER_AUTH" level. If Tuxedo SECURITY is configured as "NONE" or "APP_PW" then this filter will not be used for client certificate selection. The error condition described in previous paragraph will still be true even if this attribute is disabled at runtime.

The following table is a matrix table for decision to enable this single client identification filter:

The example in the previous section has this filter "disabled" since both places omitted this property.

The following example will have this filter "enabled".

<?xml version="1.0" encoding="UTF-8" ?>
<!- Sample.wsdf
-->
<Definition …>
<WSBinding id="sample_Binding">
<SOAP>
<AccessingPoints>
…
</AccessingPoints>
</SOAP>
<ServiceGroup id="SampleSrvGrp">
<Service name="GetData">
<Property name="defaultClientIdentification" value="catalina"/>
<Property name="useSingleClientIdentification" value="true" />
</Service>
</ServiceGroup>
</WSBinding>
</Definition>

<?xml version="1.0" encoding="UTF-8"?>
<!- sample.dep
-->
<Deployment xmlns="http://www.bea.com/Tuxedo/SALTDEPLOY/2007">
<WSDF>
<Import location="c:/salt/x.509/Sample.wsdf"></Import>
</WSDF>
<WSGateway>
<GWInstance id="INSTANCE1">
<Outbound>
…
</Outbound>
<Properties>
<Property name="defaultClientIdentification" value="melbourne"/>
</Properties>
</GWInstance>
</WSGateway>
<System>
<Certificate>
…
</Certificate>
</System>
</Deployment>