How to Configure SAML 2.0 for Pathgather

Read this before you enable SAML

The Pathgather application is pre-configured to pass the required custom attributes Job Title and Department (which are mapped to title and department in Okta User Base Profile) as part of the SAML assertion. These attributes are required to use SAML and perform Just in Time (JIT) provisioning for Pathgather.

Make sure that the title and department attributes are populated in the Okta User Base Profile, and also have the correct attribute mappings set with AD/LDAP. If this value is empty, Okta will pass a null values to Pathgather.

Supported Features
Configuration Steps
Notes

Supported Features

The Okta/Pathgather SAML integration currently supports the following features:

SP-initiated SSO
IdP-initiated SSO
JIT (Just In Time) Provisioning

For more information on the listed features, visit the Okta Glossary.

Configuration Steps

Generate the following IDP Metadata and save to a file named metadata.xml:
Sign into the Okta Admin Dashboard to generate this variable.
Send an email to Pathgather Support and request that they enable SAML 2.0 for your organization. Include the following with your email:
- Attach the metadata.xml file you created in step 1.
- Provide the following list of attribute keys:
```
 first_name, last_name, email, job_title, department 
```
Pathgather will process your request and enable SAML for your account.
Done!

Notes

Make sure that you entered the correct value in the Pathgather Base URL field under the General tab in Okta. Using the wrong value will prevent you from authenticating via SAML to Pathgather.

The following SAML attributes are supported:

Name	Value
first_name	user.firstName
last_name	user.lastName
email	user.userName

SP-initiated SSO

Go to your Pathgather URL

For example: https://[subdomain].pathgather.com