Page created: 2 Nov 2021
|
Page updated: 14 Dec 2021
Learn how to enable SumoLogic sign on from a PingFederate URL (IdP-initiated sign on) and direct SumoLogic sign on using PingFederate (SP-initiated sign on).
- Configure PingFederate to authenticate against an identity provider (IdP) or datastore containing the users requiring application access.
- PingFederate’s X.509 certificate should be exchanged to verify the signature in SAML assertions.
- An email attribute is required in the assertion, either the SAML Subject or another SAML attribute per the SAML configuration. The value of the email attribute must be a valid email address. It is used to uniquely identify the user in the organization.
- Populate SumoLogic with at least one user to test access.
-
Create a PingFederate
service provider (SP) connection for SumoLogic:
-
Add the PingFederate IdP
Connection to SumoLogic:
-
Update the ACS URL values in PingFederate:
- Sign on to the PingFederate administrative console.
- Edit the SP connection for SumoLogic.
- Set the Partner's Entity ID (Connection ID) value to SumoLogic’s Entity ID that you copied previously.
- Set Assertion Consumer Service URL : Endpoint URL to SumoLogic’s Assertion Consumer Service URL value.
- Click Save.
-
Test the PingFederate
IdP-initiated SSO integration:
-
Test the PingFederate
SP-initiated SSO integration: