Configuring a SAML application in PingFederate
Configure a SAML application in PingFederate.
Before you begin
Component
-
PingFederate 10.1
Make sure you have the following:
-
A datastore connection
-
A configured password credential validator (PCV)
-
A configured identity provider (IdP) adapter.
-
An IdP digital signing certificate
Steps
-
In the PingFederate administrative console, go to Applications > Integration > SP Connections.
-
Click Create Connection.
-
On the Connection Template tab, click Do not use a template for this connection. Click Next.
-
On the Connection Type tab, select the Browser SSO Profiles checkbox.
-
In the Protocol list, select SAML 2.0. Click Next.
-
On the Connection Options tab, leave the Browser SSO checkbox selected, and then click Next.
-
On the Import Metadata tab, import service provider (SP) metadata, pull from a URL, or enter the data manually. Click Next.
In this example, we assume that SP metadata is provided.
-
On the General Info tab, provide a Connection Name if needed and review the information. Click Next.
Entity ID and Base URL should be provided by the SP.
-
On the Browser SSO tab, click Configure Browser SSO.
-
On the SAML Profiles tab, select the IdP-Intitiated SSO and SP-Initiated SSO checkboxes. Click Next.
-
On the Assertion Lifetime tab, leave the default entries, and then click Next.
-
On the Assertion Creation tab, click Configure Assertion Creation.
-
On the Identity Mapping tab, click Standard. Click Next.
-
On the Attribute Contract tab, ensure that whatever attributes you need for the SP are defined here. Click Next.
-
On the Authentication Source Mapping tab, click Map New Adapter Instance.
-
On the Adapter Instance tab, from the Adapter Instance list, select your previously configured HTML form adapter. Click Next.
-
On the Mapping Method tab, leave the default selection, and then click Next.
-
On the Attribute Contract Fulfillment tab, from the Source list for SAML_SUBJECT, select Adapter.
-
From the Value list, depending on what the SP is expecting, select mail or uid.
-
Define any other mappings as needed. Click Next.
You can leverage hard-coded “Text” for sending values to the SP connection.
-
On the Issuance Criteria tab, click Next.
-
On the Summary tab, review your entries, and then click Done.
-
On the Authentication Source Mapping tab, click Next.
-
On the Summary tab, review your entries, and then click Done.
-
On the Assertion Creation tab, click Next.
-
On the Protocol Settings tab, click Configure Protocol Settings.
-
On the Assertion Consumer Service URL tab, ensure you see an entry for your SP based on the metadata that you uploaded. Click Next.
-
On the Allowable SAML Bindings tab, POST should be selected. Click Next.
-
On the Signature Policy tab, click Always Sign the SAML Assertion. Click Next.
-
On the Encryption Policy tab, click None. Click Next.
-
On the Summary tab, review your entries, and then click Done.
-
On the Protocol Settings tab, click Next.
-
On the Summary tab, review your entries, and then click Done.
-
On the Browser SSO tab, click Next.
-
On the Credentials tab, click Configure Credentials.
-
On the Digital Signature Settings tab, from the Signing Certificate list, select your organization’s default signing certificate that you previously created.
-
Select the Include the Certificate in the Signature <KeyInfo> Element check-box. Click Next.
-
On the Summary tab, review your entries, and then click Done.
-
On the Credentials tab, click Next.
-
On the Activation & Summary tab, click the toggle to enable the connection, and then scroll to the bottom and click Save.
The connection status is enabled when the toggle is green. You must click Save or your work will be lost.
Next steps
Click on the SP connection that you just created and copy the SSO-URL link. Start a private browsing session and test your connection using the SSO-URL link.