Identifying the SP - PingFederate - 11.2

PingFederate Server

bundle
pingfederate-112
ft:publication_title
PingFederate Server
Product_Version_ce
PingFederate 11.2
category
Administrator
Administratorguide
Audience
Capability
ContentType
DeploymentMethod
Guide
Product
Productdocumentation
SingleSignonSSO
Software
SystemAdministrator
pf-112
pingfederate
ContentType_ce
Guide
Guide > Administrator Guide
Product documentation

On the General Info tab, you provide your partner's unique federation identifier, the display name of the connection, and some other optional information, such as virtual server IDs, contact information, and logging mode for runtime transaction logging.

  1. For information on initial steps for managing SP connections, see Choosing an SP connection type.
  2. Provide the basic information to identify your partner.

    See the following table for more information.

    Field Description
    Partner's Entity ID, Issuer, Partner's Realm, or Connection ID

    (Required)

    The published, protocol-dependent, unique identifier of your partner.

    For a SAML 2.0 connection, this is your partner's SAML Entity ID.

    For a SAML 1.x connection, this is the Audience your partner advertises. This ID may have been obtained out-of-band or using a SAML metadata file.

    For a WS-Federation connection, this is your partner's Realm.

    For a security token service (STS)-only connection, you can designate any unique identifier.

    Connection Name

    (Required)

    A plain-language identifier for the connection. For example, a company or department name. This name is displayed in the connection list on the administrative console.
    Virtual Server IDs If you want to identify your server to this connection partner using an ID other than the one you specified at System > Server > Protocol Settings > Federation Info, enter a virtual server ID in this field and click Add.

    Enter additional virtual server IDs as needed.

    Base URL The fully qualified host name and port on which your partner's federation deployment runs. For example, https://www.example.com:9031. This entry is an optional convenience, allowing you to enter relative paths to specific endpoints, instead of full URLs, during the configuration process.
    Company The name of the partner company to which you are connecting.
    Contact Name The contact person at the partner company.
    Contact Number The phone number of the contact person at the partner company.
    Contact Email The email address for the contact person at the partner company.
    Application Name The name of the application, accessible through the IdP Adapter interface IdpAuthenticationAdapterV2 in the PingFederate Java SDK.

    This field is not applicable to an STS-only connection.

    Application Icon URL The URL of the application icon, accessible through the IdP Adapter interface IdpAuthenticationAdapterV2 in the PingFederate Java SDK.

    Note that this field is not applicable to an STS-only connection.

    Logging Mode The level of transaction logging applicable for this connection.
  3. After entering the relevant identification information, click Next.