Configuration Guides › Federation Security Services Guide › Use SAML 2.0 Provider Metadata To Simplify Configuration › Export Metadata Tool

Export Metadata Tool

You can use the export tool in the following situations:

• Create an Identity Provider metadata file for use by Service Providers

  Use the tool to produce a metadata file containing information about profiles supported by the Identity Provider. This XML output that the export tool generates describes the Identity Provider. Sites acting as Service Providers can import this metadata file to establish a relationship with the Identity Provider.

• Create an Identity Provider metadata file based on an existing Service Provider

  A SOA Security Manager Identity Provider generates a metadata file based on an existing Service Provider object. The use of the Service Provider object reduces the amount of required data that a user must configure. Many of the settings for the Identity Provider metadata file can be derived from the existing Service Provider. Also,SOA Security Manager provides the default names of the servlets.

  To use the metadata file, the existing relationship between the Identity Provider and the Service Provider is similar to the relationship you are establishing.

  The SSO and SLO servlet URLs are the default servlet names prepended with the IP address and port of the Federation Web Services application.

  The servlet names are:

  • http://idp_server:port/affwebservices/public/saml2sso
  • http://idp_server:port/affwebservices/public/saml2slo

  idp_server:port

  Identifies the web server and port hosting the Web Agent Option Pack or SPS federation gateway.

• Create a Service Provider metadata file for Use by Identity Providers

  A SOA Security Manager Service Provider can facilitate federation with sites acting as Identity Providers by producing a metadata file containing information about the profiles it supports. An Identity Provider can import the metadata file to establish a relationship with the Service Provider.

• Create a Service Provider metadata file based on an existing SAML 2.0 Authentication Scheme

  A SOA Security Manager Service Provider generates a metadata file based on an existing SAML 2.0 Authentication Scheme object. The use of the Service Provider object reduces the amount of required data that a user must configure. Many of the settings for the SP metadata file can be derived from the existing SAML 2.0 authentication scheme. SOA Security Manager provides the default names of the servlets.

  To use the metadata file, the existing relationship between the Service Provider and the Identity Provider must be similar to the relationship you are establishing. The SSO and SLO servlet URLs are the default servlet names prepended with the IP address and port of the Federation Web Services application.

  The servlets are:

  • http://idp_server:port/affwebservices/public/saml2sso
  • http://idp_server:port/affwebservices/public/saml2slo

  idp_server:port

  Identifies the web server and port hosting the Web Agent Option Pack or SPS federation gateway.

The following illustration shows a metadata file generated only from user input.

The following illustration shows a metadata file that is generated from a combination of user input and data from an existing Service Provider object.