background image

Specific Message Security

<< Configuring the Application Server | message-security-binding element >>
<< Configuring the Application Server | message-security-binding element >>
244
S
ECURING
W
EB
S
ERVICES
10.To modify the message protection policies of the enabled providers, select
the Providers tab.
11.Select a provider for which to modify message protection policies. For
more description on each of the fields on the Edit Provider Configuration
page, select Help from the Admin Console.
12.Click Save and restart the Application Server if so indicated.
Configuring Application-Specific Message
Security
Application-specific web services message security functionality is configured
(at application assembly) by adding
message-security-binding
elements to
the web service endpoint. The
message-security-binding
elements are added
to the runtime deployment descriptors of the application (
sun-ejb-jar.xml
,
sun-web.xml
, or
sun-application-client.xml
). These
message-security-
binding
elements are used to associate a specific provider or message protection
policy with a web services endpoint or service reference, and may be qualified so
that they apply to a specific port or method of the corresponding endpoint or ref-
erenced service.
The following is an example of a
sun-ejb-jar.xml
deployment descriptor file
to which a
message-security-binding
element has been added:
<sun-ejb-jar>
<enterprise-beans>
<unique-id>1</unique-id>
<ejb>
<ejb-name>HelloWorld</ejb-name>
<jndi-name>HelloWorld</jndi-name>
<webservice-endpoint>
<port-component-name>HelloIF</port-component-name>
<endpoint-address-uri>service/HelloWorld</endpoint-
address-uri>
<message-security-binding auth-layer="SOAP">
<message-security>
<message>
<java-method>
<method-name>ejbTaxCalc</method-name>
</java-method>
</message>
<message>
<java-method>
<method-name>sayHello</method-name>