This article describes how to configure the NeoGov application in Okta using Security Assertion Markup Language (SAML).
- Custom SAML app
- SAML 2.0
- NeoGov
- Okta Classic Engine
NOTE: The configuration presented below applies only to NeoGov production instances.
- Please follow the instructions on how to configure a Custom SAML app in Okta.
- Uncheck the Use this for Recipient URL and Destination URL, and populate the following URLs:
- Single Sign On URL: https://login.neogov.com/authentication/saml/consumer
- Recipient URL: https://login.neogov.com/authentication/saml/login/[provide company ID from Neogov]
- Destination URL: https://login.neogov.com/authentication/saml/consumer
- Audience Restriction: https://login.neogov.com/ (make sure to add the slash at the end for this URL)
- Set the NameID format to Persistent and the Application username to Okta username, then assign the application to the user account/accounts.
- Ensure that the username set in the NeoGov assignment in Okta matches the one configured on NeoGov's side.
- The metadata can be retrieved by navigating to the NeoGov app in Okta and clicking the Identity Provider metadata link located under the Sign On tab. Afterward, send the information to the Service Provider's Support Team.
