To enable message security for the Application Server, you first specify a provider to be used by default on the server side and a provider to be used by default on the client side for any application for which a specific provider has not been bound. After you enable the default providers for message security, you also need to enable the providers used by your clients or the Application Server will reject your requests. Information for enabling the providers used by clients is discussed in "Enabling Message Security for Client Applications".
To enable the default client and server providers for the Application Server, follow these steps.
server
, select the server-config
node.default-config
node.
By default, no provider configuration is selected for the Application Server. To identify a server-side provider, select ClientProvider
or ServerProvider
. You can also leave this field set to or select the null option. Selecting the null option means that no message security provider will be invoked on the server side.
You would generally select ServerProvider
for this field.
By default, no provider configuration is selected for the Application Server. To identify a client-side provider, select ClientProvider
or ServerProvider
. You can also leave this field set to or select the null option. Selecting the null option means that no message security provider will be invoked on the client side.
You would generally select ClientProvider
for this field.
Equivalent asadmin commands:
asadmin set --user <admin-user> --port <admin-port>
server-config.security-service.message-security-config.SOAP.
default_provider=ServerProvider
asadmin set --user <admin-user> --port <admin-port>
server-config.security-service.message-security-config.SOAP.
default_client_provider=ClientProvider
See also: