Set up Okta SSO

Updated

Who can do this: Super Admins

Connect Okta to OnRamp with SAML so your team signs in with their Okta accounts. When you're done, OnRamp sends people to Okta to sign in.

This feature is available when it's turned on for your organization. If you don't see it, contact your OnRamp team.

Before you begin

  • You need admin access to your Okta organization.

  • Each person who signs in needs an active OnRamp account with the same email address they use in Okta.

  • If your organization uses Google SSO, saving SAML SSO replaces it. Only one SSO provider can be saved at a time. For Google, see Enable Google SSO for your OnRamp organization.

Get OnRamp's SAML values

  1. Go to Settings > Single sign-on. It's listed under the Organization group.

  2. Turn on Enforce SAML SSO.

  3. Copy the Assertion Consumer Service URL and the SAML Entity ID. Keep this tab open while you set up Okta.

Create the OnRamp app in Okta

  1. In Okta, create a SAML 2.0 app integration for OnRamp.

  2. Paste the Assertion Consumer Service URL into the app's single sign-on URL.

  3. Paste the SAML Entity ID into the app's audience URI (SP entity ID).

  4. Set the app to send each user's email address. OnRamp matches people by the email in the SAML response.

  5. Assign the people who'll sign in to OnRamp to the app.

  6. Copy the app's metadata URL.

Finish setup in OnRamp

  1. Go back to Settings > Single sign-on.

  2. Keep SAML (Metadata) (Recommended) selected.

  3. In SAML Metadata URL, paste the metadata URL from Okta. It must be a valid URL before you can save.

  4. In the bar that shows You have unsaved changes, select Save changes.

When it works, a message reads "SSO configuration saved". If you leave the page before saving, OnRamp asks Leave without saving?

Note: If you'd rather not use a metadata URL, select SAML (Manual). Then enter the Identity Provider HTTP POST URL and x.509 Certificate from Okta, plus an Identity Provider Logout URL (optional).

The same section has Enable SSO for customer users, which applies this SSO to the customer portal. For how customer users sign in, see How customers authenticate and access the portal.

How signing in works

People can start from OnRamp or from the OnRamp tile in Okta. Either way, OnRamp looks for an active OnRamp user with the email Okta sends. If there isn't one, the person can't get in. Someone has to exist in both Okta and OnRamp.

If someone can't sign in:

  • Check that their email address is the same in Okta and OnRamp.

  • Check that they have an active OnRamp account.

  • Check that they're assigned to the OnRamp app in Okta.

  • Check that the metadata URL in OnRamp matches the one in Okta.

Turn off SAML SSO

  1. Go to Settings > Single sign-on.

  2. Turn off Enforce SAML SSO.

  3. Select Save changes.

Saving removes the SAML connection.

More in Integration Setup & Authentication