Viewing Partner Site, Certificate, and Service Endpoint Information

7-18 Securing Oracle WebLogic Server WebLogic Server provides the com.bea.security.saml2.providers.registry.WebSSOIdPPartner Java interface for configuring this attribute.

7.3.4.5.5 Configure 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 method. 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 URL of the custom web application that generates the POST form for carrying the SAML response for POST bindings to this Identity Provider partner. ■ The URL of the custom web application that generates the POST form for carrying the SAML response for Artifact bindings to this Identity Provider partner. 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 this Identity 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.5 Viewing Partner Site, Certificate, and Service Endpoint Information

When you configure SAML 2.0 partners, the partner configuration pages displayed by the Administration Console include tabs for viewing and configuring the following additional information about the partner: ■ The Site tab displays information about the Service Provider partner, which is derived from the partners metadata file. The data in this tab is read-only. WebLogic Server provides the com.bea.security.saml2.providers.registry.MetadataPartner Java interface for partner site information. ■ The Single Sign-On Signing Certificate tab displays details about the partners signing certificate, which are also derived from the partners metadata file. The data in this tab is read-only. Operations on these attributes are available from the com.bea.security.saml2.providers.registry.WebSSOPartner Java interface. ■ The Transport Layer Client Certificate tab displays partners transport layer client certificate. You can optionally import this certificate by clicking Import Certificate from File . Note: If you configure one or more redirect URIs, remember to set a security policies on them as well; otherwise the web container will not attempt to authenticate the user and, consequently, not redirect the user’s request to the Identity Provider partner. Configuring Single Sign-On with Web Browsers and HTTP Clients 7-19 Operations on this attribute are available from the com.bea.security.saml2.providers.registry.BindingClientPartne r Java interface. ■ When configuring Service Provider partners, the Assertion Consumer Service Endpoints tab is available, which displays the Service Provider partners ACS endpoints. This data is also available from the com.bea.security.saml2.providers.registry.WebSSOSPPartner Java interface. ■ When configuring Identity Provider partners, the Single Sign-On Service Endpoints tab is available, which displays the Identity Provider partners single sign-on service endpoints. This data is also available from the com.bea.security.saml2.providers.registry.WebSSOIdPPartner Java interface. ■ The Artifact Resolution Service Endpoints tab displays the partners ARS endpoints. This data is also available from the com.bea.security.saml2.providers.registry.WebSSOPartner Java interface.

7.3.6 Web Application Deployment Considerations for SAML 2.0