You use the AM Security tab of the Web Service Attributes Editor to enable and configure a SAML security mechanism for web service clients.
To enable a SAML security mechanism for a web service client:
In the Projects window, expand the project node for the project where your web service client is defined.
Expand the Web Service References node and right-click the web-service-information node and choose Edit Web Service Attributes from the pop-up menu.
The Web Service Attributes Editor opens with the AM Security tab open.
Select the Enable Message Level Security checkbox.
Under Security Mechanism, from the Request drop-down list, select SAML-HolderOfKey or SAML-SenderVouches.
To specify that response verification is required, select the Verify Response checkbox.
Under Existing Certificate Settings, to use a custom keystore, clear the Use Default Key Store checkbox and enter the required information.
You can use the Browse button to navigate to and select a different location for the keystore file.
If you use the default keystore for the web service client, you must also use the default keystore for the web service provider.
From the Server drop-down list, select the Access Manager server instance that is associated with the Sun Java System Application Server for your project.
Click OK.
To be able to deploy the client and the provider to two different Access Manager instances, the public key or the certificate authority (CA) of the web service client must be added to the trusted list of certificates or certificate authorities of the web service providers respectively.
If you are using the configuration wizards in the IDE and the web service client and web service provider both point to the same Access Manager, this manual step is not needed.