Typically, a provider would be re-configured to modify its message protection policies, although the provider type, implementation class, and provider-specific configuration properties may also be modified.
The Message Security Configurations page opens.
By default, the only configured message security configuration is SOAP.
The Edit Message Security Configuration page opens.
The Provider Configurations page opens.
By default, four providers are configured for the SOAP authentication layer.
The Edit Provider Configuration page appears.
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.
Available choices are:
Specifies that the provider is the client authentication provider.
Specifies that the provider is the server authentication provider.
Specifies that the provider is both a client and a server authentication 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.
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.
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.
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.
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.
For a description of the additional properties available for provider configurations, see Properties Specific to Message Security Provider Configurations.
See Also
Copyright © 2005, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices