Configure the NeoGov Application in Okta Using SAML

Administrators can configure the NeoGov application in Okta using a custom Security Assertion Markup Language (SAML) integration. This configuration applies specifically to NeoGov production instances and requires usernames to match between Okta and NeoGov.

• Okta Identity Engine (OIE)
• Okta Classic Engine
• NeoGov
• Custom SAML Application
• Security Assertion Markup Language (SAML) 2.0

How is the NeoGov application configured in Okta using SAML?

Create a custom SAML application in the Okta Admin Console, configure the specific NeoGov Single Sign-On URLs and audience restrictions, and provide the Identity Provider metadata to NeoGov Support.

1. Create a custom SAML application by following the How To Configure A Custom SAML App documentation.
2. Clear the Use this for Recipient URL and Destination URL checkbox during the SAML configuration.
3. Enter https://login.neogov.com/authentication/saml/consumer in the Single Sign On URL field.
4. Enter https://login.neogov.com/authentication/saml/login/<company_ID> in the Recipient URL field, replacing <company_ID> with the company ID provided by NeoGov.
5. Enter https://login.neogov.com/authentication/saml/consumer in the Destination URL field.
6. Enter https://login.neogov.com/ in the Audience Restriction field.
   • NOTE: The Audience Restriction URL must include the trailing slash.
7. Select Persistent from the Name ID format dropdown menu.
8. Select Okta username from the Application username dropdown menu.
9. Assign the application to the required users and ensure the Okta username matches the username configured in NeoGov.

Review the following image for an example of the General SAML Settings.

10. Navigate to the Sign On tab of the NeoGov application in Okta.
11. Select the Identity Provider metadata link to retrieve the metadata.
12. Send the retrieved metadata to the NeoGov Support team to complete the configuration.