en.help.task-messagesecurityproviderconfignew.html Maven / Gradle / Ivy
To Create a Message Security Provider Configuration
To create a new message security provider configuration, follow these steps:
- In the navigation tree, expand the Configuration node.
- Expand the Security node.
- Select the Message Security node.
The Message Security Configurations page opens.
- On the Message Security Configurations page, click the Authentication Layer name of the
configuration that you are editing.
By default, the only configured message security configuration is SOAP.
The Edit Message Security Configuration page opens.
- Click the Providers tab.
The Provider Configurations page opens.
- On the Provider Configurations page, click New.
The New Provider Configuration page appears.
- On the New Provider Configuration page, in the Provider ID field, type a
unique name for the provider configuration.
- Select the Default Provider checkbox to make this provider the default provider.
The default provider will be invoked for any application that does not identify
a specific provider. Whether the provider is the default client provider, the default
server provider, or both is determined by the Provider Type.
- From the Provider Type drop-down list, select the provider type.
Available choices are:
- client
Specifies that the provider is the client authentication provider.
- server
Specifies that the provider is the server authentication provider.
- client-server
Specifies that the provider is both a client and a server authentication provider.
- In the Class Name field, type the name of the Java implementation class
of the provider.
Client authentication providers must implement the com.sun.enterprise.security.jauth.ClientAuthModule interface. Server-side providers must implement the com.sun.enterprise.security.jauth.ServerAuthModule
interface. Client-server providers must implement both interfaces.
- In the Request Policy area, from the Authenticate Source drop-down list, select the
type of required authentication for the request policy.
The request policy determines the request processing that the authentication provider performs. The
request policy fields are optional, but if they are not specified, the authentication
provider does not authenticate request messages.
Select sender to specify message-layer sender authentication (for example, username and password) of
request messages. Select content to specify content authentication (for example, digital signature) of
request messages. Leave the field empty to not authenticate the source of requests.
By default, no authentication type is selected.
For a description of the actions performed by the SOAP message security providers,
see Request and Response Policy Configurations.
- From the Authenticate Recipient drop-down list, select whether recipient authentication occurs before or
after content authentication for the request policy.
Select before-content or after-content to require message-layer authentication of the receiver of the
request message to its sender (by XML encryption). If the value is not
specified, the default is after-content. Policies are expressed in message sender order, so
after-content means that the message receiver decrypts the message before validating the signature.
- In the Response Policy area, from the Authenticate Source drop-down list, select the
type of required authentication for the response policy.
The response policy determines the response processing that the authentication provider performs. The
response policy fields are optional, but if they are not specified, no authentication
is applied to response messages.
Select sender to specify message-layer sender authentication (for example, username password) of response
messages. Select content to specify content authentication (for example, digital signature) of response messages.
Leave the field empty to not authenticate response sources. By default, no authentication
type is selected.
For a description of the actions performed by the SOAP message security providers,
see Request and Response Policy Configurations.
- From the Authenticate Recipient drop-down list, select whether recipient authentication occurs before or
after content authentication for the response policy.
Select before-content or after-content to define a requirement for message-layer authentication of the
receiver of the response message to its sender (by XML encryption). If the
value is not specified, the default is after-content. Policies are expressed in message
sender order, so after-content means that the message receiver decrypts the message before
validating the signature.
- (Optional) In the Additional Properties section, specify additional properties.
To add a property, click the Add Property button. In the blank row
that appears, type the property name in the Name field, and type the
property value in the Value field.
For a description of the additional properties available for provider configurations, see Properties Specific to Message Security Provider Configurations.
- Click OK.
See Also