To create a new message security provider, follow these steps. Steps beginning with EE: are specific to the Enterprise Edition of the Application Server. Steps beginning with PE: are specific to the Platform Edition of the Application Server.
client
, server
, or client-server
to establish whether the provider is to be used as a client authentication provider, a server authentication provider, or both (a client-server provider). The default value is client-server
.com.sun.enterprise.security.jauth.ClientAuthModule
interface. Server-side providers must implement the com.sun.enterprise.security.jauth.ServerAuthModule
interface. A provider may implement both interfaces, but it must implement the interface corresponding to its provider type.sender
or content
to define a requirement for message-layer sender authentication (e.g. username password) or content authentication (e.g. digital signature) to be applied to request messages. When this argument is not specified, source authentication of the request is not required.beforeContent
or afterContent
to define a requirement for message-layer authentication of the receiver of the request message to its sender (e.g. by XML encryption). When the value is not specified it defaults to afterContent
.sender
or content
to define a requirement for message-layer sender authentication (e.g. username password) or content authentication (e.g. digital signature) to be applied to response messages. When this argument is not specified, source authentication of the response is not required.beforeContent
or afterContent
to define a requirement for message-layer authentication of the receiver of the response message to its sender (e.g. by XML encryption). When the value is not specified it defaults to afterContent
.server.config
: the directory and file name of an XML file that contains the server configuration information. For the default provider, this value is install_dir/
domain_dir/config/wss-server-config.xml
.See also: