Request receiver binding collection
Use this page to specify the binding configuration to receive request messages for Web services security.
To view this administrative console page, complete the following steps...
- Click Applications > Enterprise Applications > appname.
- Under Related Items, click Web Modules > URI_file_name > Web Services: Server Security Bindings.
- Under Request Receiver Binding, click Edit.
Signing Information Specifies the configuration for the signing parameters. Signing information is used to sign and validate parts of a message including the body, the time stamp, and the user name token.
You also can use these parameters for X.509 certificate validation when the authentication method is IDAssertion and the ID Type is X509Certificate in the server-level configuration. In such cases, fill in the Certificate Path fields only.
Encryption Information Specifies the configuration for the encrypting and decrypting parameters. This configuration is used to encrypt and decrypt parts of the message that include the body and the user name token.
Trust Anchors Specifies a list of key store objects that contain the trusted root certificates that are issued by a certificate authority (CA).
The certificate authority authenticates a user and issues a certificate. The CertPath API uses the certificate to validate the certificate chain of incoming, X.509-formatted security tokens or trusted, self-signed certificates.
Collection Certificate Store Specifies a list of the untrusted, intermediate certificate files.
Key Locators Specifies a list of key locator objects that retrieve the keys for digital signature and encryption from a key store file or a repository. The key locator maps a name or a logical name to an alias or maps an authenticated identity to a key. This logical name is used to locate a key in a key locator implementation.
Trusted ID Evaluators Specifies a list of trusted ID evaluators that determine whether to trust the identity-asserting authority or message sender.
The trusted ID evaluators are used to authenticate additional identities from one server to another server. For example, a client sends the identity of user A to server 1 for authentication. Server 1 calls downstream to server 2, asserts the identity of user A, and includes the user ID and password of server 1. Server 2 attempts to establish trust with server 1 by authenticating its user ID and password and checking the trust based on the TrustedIDEvaluator implementation. If the authentication process and the trust check are successful, server 2 trusts that server 1 authenticated user A and a credential is created for user A on server 2 to invoke the request.
Login Mappings Specifies a list of configurations for validating tokens within incoming messages.
See AlsoRequest receiver
Securing Web services using XML encryption
Configuring the server for request digital signature verification: verifying the message parts
Configuring the server for request digital signature verification: choosing the verification method
Configuring the server for request decryption: Decrypting the message parts
Configuring the server for request decryption: choosing the decryption method
Encryption information collection