Connect Okta to Venn for Identity and User Management

In order to enable seamless user and permissions management in Venn, Venn offers integrations with third-party Identity Providers (IdPs), including Okta.

If you configure Okta as your Venn Identity Management solution, you will set up SAML-based Identity Management so that users' Venn login information will be managed through Okta. Okta also offers the option to set up SCIM provisioning, which allows you to manage user access to Venn in Okta. You may or may not choose to set up SCIM provisioning depending on your company’s Okta subscription type.

Learn how to manage Venn user access with Okta as your IdP.

Requirements for SCIM Provisioning

User Provisioning Requirements

In order to successfully sync over users, your Okta user records must include these required fields:

  • First Name (user.firstName in Okta)
  • Last Name (user.lastName in Okta)
  • Email (user.email in Okta)

Additionally, your Okta users' Application usernames must meet the following criteria:

  • Length: The string must be between 2 and 40 characters long.
  • Allowed characters:
    • Numbers 0-9
    • Uppercase letters A-Z
    • Lowercase letters a-z
    • Hyphen/dash -
    • Underscore _

The Okta field that you are using as the Application username for Venn can be viewed and adjusted on the Sign On tab of the Venn app you create in Okta. 

Any users in Okta that do not meet this criteria will fail to provision. 

Group Provisioning Requirements (Optional)

You may choose to assign the Venn app by group in Okta rather than assigning it to individual users.

In order to successfully sync over groups, your Okta groups' group.name values must meet the following criteria:

  • Length: The string must be between 3 and 18 characters long.
  • Allowed characters:
    • Numbers 0-9
    • Uppercase letters A-Z
    • Lowercase letters a-z
    • Hyphen/dash -
    • Underscore _
    • Space   (can be in any position)

Any groups with names that do not meet this criteria will fail to provision. 

Set up Okta as Your IdP

You must have Admin access to Okta in order to set it up as your Venn IdP.

If you already have Identity Management configured in Venn, changing your identity provider will result in all users being locked out of Venn, including Company Managers. For that reason, changes should only be made in collaboration with the Venn team or a Venn partner.

To set up Okta as your IDP: 

  1. The Venn team or a Venn partner will guide you through the process of changing your Identity Provider to Okta in Venn's Company Admin.
  2. After your Identity Provider has been changed to Okta in Venn's Company Admin, log in to Okta with an account that has administrator permissions to complete the IdP setup.
  3. In the menu at left, click Applications and select Applications.

    Picture1.png

  4. Click Create App Integration.

    Picture2.png

  5. Select SAML 2.0 as the sign-in method and click Next.

    Picture3.png

  6. On the next page, enter “Venn” in the App name field, upload the file found here in the App logo (optional) field and click Next.

    Picture5.png

  7. Input the following in the Single sign on URL and the Audience URL (SP Entity ID) fields: https://[company shortname].venn.com/sso/okta (replace [company shortname] with your company's shortname in Venn, which is the abbreviation for your company that you see in the URL bar before .venn.com when you have the Workplace web app open). Then, click Continue.

    Picture8.png

  8. Select I’m an Okta customer adding an internal app and click Finish

    Picture9.png

  9. You will be brought to the Sign On tab for the newly created Venn application in Okta. Click View Setup Instructions under Settings or View SAML Setup Instructions in the panel at right.

    Picture15.pngOkta_View Setup Instructions2.png

  10. Scroll down to the Optional section and copy all IdP metadata.
  11. Add the IdP metadata from Okta to the Okta Identity Provider settings in Venn.
    1. Navigate to login.venn.com and sign in using the Admin temporary account provided by your Venn team.
    2. Click Company admin or Manage > Company admin.

      Updated_CM.png

    3. Click All websites.

      Company Admin_All Websites.jpg

    4. Click Okta in the websites list and click Edit Identity Provider.

      Okta_Edit Provider.jpg

    5. Paste the metadata into the IdP metadata field and click Save

      Okta_Add metadata.jpg

Once these steps are complete, Okta will be set up as you IdP for Venn.

Set up SCIM Provisioning

After you have set up Okta as your IdP, you can set up SCIM provisioning, which allows you to manage user access to Venn in Okta.

  1. In Okta, go to the General tab for the Venn application that you created.
  2. Click Edit under App Settings, select Enable SCIM provisioning, and then click Save. This will add a Provisioning tab for the Okta application.
  3. In Venn, generate the token you need to set up SCIM provisioning.
    1. Navigate to login.venn.com and sign in using the Admin temporary account provided by your Venn team.
    2. Click Company admin or Manage > Company admin.

      Updated_CM.png

    3. Click All websites.

      Company Admin_All Websites.jpg

    4. Click Okta in the websites list and click Edit Identity Provider.

      Okta_Edit Provider.jpg

    5. Click Generate token and copy it.

      Okta_Generate Token.jpg

  4. In Okta, navigate to the Provisioning tab for the Venn application.

    Picture10.png

  5. Click Edit under SCIM Connection. Configure with the information below:
    • SCIM connector base URL: https://login.venn.com/scim
    • Unique identifier field for users: userName
    • Check the box to enable Push new users
    • Check the box to enable Push Profile Updates
    • Check the box to enable Push Groups (if needed)
    • Authentication Mode: HTTP Header
    • Authorization: Paste the token from the Venn team

      Picture11.png

  6. Click Test Connector Configuration

    Picture12.png

  7. Click Save.
  8. Navigate to the Provisioning tab. Keep the following attributes mapped on the Provisioning tab. Remove all other Attributes from the mapping.

    userName Configured in Sign On settings
    givenName user.firstName
    familyName user.lastName
    middleName user.middleName
    email user.email
    emailType (user.email != null && user.email != '') ? 'work' : ''
    primaryPhone user.primaryPhone
    primaryPhoneType (user.primaryPhone != null && user.primaryPhone != '') ? 'work' : ''
  9. Click Edit.
  10. In the Provisioning to App section, check the boxes to enable Create Users, Update User Attributes, and Deactivate Users and then click Save.

    Picture14.png

Once these steps are complete, users will be provisioned into Venn from Okta.

Manage User Access to Venn when Okta is Your IdP

Follow the steps in this article to manage user access to Venn once you have set up Okta as your IdP.

Was this article helpful?