The following topics are addressed here:
Use the create–message–security–provider subcommand in remote mode to create a new message provider for the security service. If the message layer does not exist, the message layer is created, and the provider is created under it.
Ensure that the server is running.
Remote subcommands require a running server.
Create the message security provider by using the create-message-security-provider(1) subcommand.
Information about properties for this subcommand is included in this help page.
(Optional) If needed, restart the server.
Some properties require server restart. See Configuration Changes That Require Server Restart. If your server needs to be restarted, see To Restart a Domain.
This example creates the new message security provider mySecurityProvider.
asadmin> create-message-security-provider --classname com.sun.enterprise.security.jauth.ClientAuthModule --providertype client mySecurityProvider Command create-message-security-provider executed successfully. |
You can also view the full syntax and options of the subcommand by typing asadmin help create–message–security–provider at the command line.
Use the list–message–security–providers subcommand in remote mode to list the message providers for the security layer.
Ensure that the server is running.
Remote subcommands require a running server.
List the message security providers by using the list-message-security-providers(1) subcommand.
This example lists the message security providers for a message layer.
asadmin> list-message-security-providers --layer SOAP XWS_ClientProvider ClientProvider XWS_ServerProvider ServerProvider Command list-message-security-providers executed successfully. |
You can also view the full syntax and options of the subcommand by typing asadmin help list–message–security–providers at the command line.
Ensure that the server is running.
Remote subcommands require a running server.
List the message security providers by using the list-message-security-providers(1) subcommand.
Modify the values for the specified message security provider by using the set(1) subcommand.
The message security provider is identified by its dotted name.
Use the delete-message-security-provider subcommand in remote mode to remove
Ensure that the server is running.
Remote subcommands require a running server.
List the message security providers by using the list-message-security-providers(1) subcommand.
Delete the message security provider by using the delete-message-security-provider(1) subcommand.
This example deletes the myServerityProvider message security provider.
asadmin> delete-message-security-provider --layer SOAP myServerityProvider Command delete-message-security-provider executed successfully. |
You can also view the full syntax and options of the subcommand by typing asadmin help delete–message–security–provider at the command line.