Configure How Documents Are Signed You can use the General tab of the Service Configure Artifact Binding and Transport Settings Optionally, you also use the

7-14 Securing Oracle WebLogic Server ■ Whether the assertions sent to this partner must be disposed of immediately after use ■ Whether this servers signing certificate is included in assertions generated for this partner WebLogic Server provides the com.bea.security.saml2.providers.registry.SPPartner Java interface for configuring these attributes.

7.3.3.3.4 Configure How Documents Are Signed You can use the General tab of the Service

Provider partner configuration page to determine how the following documents exchanged with this partner must be signed: ■ Assertions Operations on this attribute are available in the com.bea.security.saml2.providers.registry.SPPartner interface. ■ Authentication requests Operations on this attribute are available in the com.bea.security.saml2.providers.registry.WebSSOSPPartner interface. ■ Artifact requests Operations on this attribute are available in the com.bea.security.saml2.providers.registry.WebSSOPartner interface. The attributes for specifying whether this partner accepts only signed assertions, or whether authentication requests must be signed, are read-only: they are derived from the partners metadata file.

7.3.3.3.5 Configure Artifact Binding and Transport Settings Optionally, you also use the

General tab of the Service Provider partner configuration page to configure the following: ■ Whether SAML artifacts are delivered to this partner via the HTTP POST binding. If so, you may also specify the URI of a custom web application that generates the HTTP POST form for sending the SAML artifact. ■ The URI of a custom web application that generate the HTTP POST form for sending request or response messages via the POST binding. Operations on these attributes are available via the com.bea.security.saml2.providers.registry.WebSSOPartner Java interface. For added security in the exchange of documents with this partner, you can also specify a client user name and password to be used by the Service Provider partner when connecting to the local sites binding using Basic authentication. This attribute is available via the com.bea.security.saml2.providers.registry.BindingClientPartner Java interface.

7.3.4 Configuring a Service Provider Site for SAML 2.0 Single Sign-On

This section presents the following topics: ■ Section 7.3.4.1, Configure the SAML 2.0 Identity Assertion Provider