Create a Web Service security configuration
Related Tasks Related Topics
Use this page to create a new Web Service security configuration.
When a deployed WebLogic Web Service has been configured to use message-level security (encryption and digital signatures, as described by the WS-Security specification), the Web Services runtime determines whether a Web Service security configuration is also associated with the service. This security configuration specifies information such as whether to use an X.509 certificate for identity, whether to use password digests, the keystore to be used for encryption, and so on.
WebLogic Web Services are not required to be associated with a security configuration; if the default behavior of the Web Services security runtime is adequate then no additional configuration is needed. If, however, a Web Service requires different behavior from the default (such as using an X.509 certificate for identity, rather than the default username/password token), then the Web Service must be associated with a security configuration.
The @weblogic.jws.security.WssConfiguration JWS annotation in the JWS file that implements the Web Service specifies the name of the security configuration that is associated with a Web Service. If the Web Service does not include this annotation, then it is associated with the default security configuration, called default_wss.
This assistant guides you through the process of creating a new Web Service security configuration.
Remember that if you are creating the default configuration, you must name it
- Create a Web Service security configuration
- Specify the key pair used to sign SOAP messages
- Specify the key pair used to encrypt SOAP messages
- Use a password digest in SOAP messages
- Use X.509 certificates to establish identity