Before you begin
Note: If you click the browser's Back button after clicking OK, the partner name is reset to the default.
A URI may include a wildcard pattern, but the wildcard
pattern must include a file type to match specific files in a
directory. For example, to create a match for all files in the
/targetapp directory, including all
.htm files, the following wildcard patterns are
/targetapp/* /targetapp/*.jsp /targetapp/*.html /targetapp/*.htm
Note also that SAML 2.0 provides alternative mechanisms for initiating a web single sign-on session when unauthenticated requests for specific resources arrive at a Service Provider site. See Configuring Single Sign-On with Web Browsers and HTTP Clients.
Note: To extract attributes from an assertion, you must create and configure a SAML Authentication provider instance in the security realm. For more information, see Configure Authentication and Identity Assertion providers and Configuring the SAML Authentication Provider.
If the Artifact binding is not enabled for this partner, no ARS endpoints information will be available.
The Identity Provider partner is created in the local server instance. The information associated with this partner obtained from the partner's metadata file is visible in the Administration Console as read-only data. Modifying this data is not recommended and may produce unpredictable results.
After you finish
Coordinate with your federated partners to ensure that the SAML bindings you have enabled for this SAML authority, as well as your requirements for signed documents, are compatible with your partners. For more information, see Configuring Single Sign-On with Web Browsers and HTTP Clients.