Before you begin
You must first create the Web Service security configuration that is associated with a Web Service before you can configure specific features.
See Create a Web Service security configuration for details about creating a security configuration.
The Default Identity Asserter of WebLogic Server is configured, by default, to use username/password tokens for authentication, and is not configured to accept X.509 certificates. Client applications that invoke a Web Service use the Default Identity Asserter for authentication, by default.
However, a programmer can specify (using security assertions in the WS-SecurityPolicy file associated with a Web Service) that a client application invoking the service should use X.509 certificates as tokens to establish identity. To enable this functionality, you must configure the Web Service security configuration associated with the service, as well as configure the Default Identity Asserter.
Caution: This task applies only to JAX-RPC 1.1 Web Services, and not to JAX-WS 2.0 Web Services.
Web Services programmers associate a Web Service security
configuration using the
value attribute specifies the
associated configuration name. If the programmer does not specify
value attribute, the Web Service is associated
with the default security configuration:
myrealmsecurity realm, displayed in the Realms table.
DefaultIdentityAsserterin the Authentication Providers table.
X.509from the Available to the Chosen box.
After you finish
You must redeploy any Web Service which is associated with this security configuration for the security changes to take effect.