SAML setup with Okta

Configuring OpenVPN Cloud user authentication to use SAML

The administrator can configure OpenVPN Cloud to authenticate access to User Portal, download of VPN profile, and VPN connections using a SAML 2.0 compliant Identity Provider.

The administrator needs to follow the steps below. The steps below use Okta as the Identity Provider. Basic configuration guides for some of the other popular Identity as a Service (IDaaS) providers are provided separately.

  1. Sign in to the OpenVPN Cloud administration portal at

    1. Navigate to Settings section and click on the User Authentication tab.

    2. Click on the Edit button positioned on the top right

    3. Click on the Configure button under the SAML option

    4. The SAML Configuration webpage opens in a new browser window/tab and show the information needed to configure OpenVPN Cloud as a Service Provider in your Identity Provider.

  2. Login to the administration console of the Identity Provider to configure OpenVPN Cloud as a SAML Service Provider. The steps for Okta are below:

    1. Navigate to Applications tab, Add Application and click on the Create New App button

    2. Select Platform as Web and SAML 2.0 as Sign on method then click on the Create button

    3. Provide an Application Name and click on the Next button. In the General tab:

      • Enter the Issuer Name displayed in the SAML Configuration webpageof OpenVPN Cloud into Audience URI (SP Entity ID) input field of Okta

      • Enter the SSO URL displayed in the SAML Configuration webpage of OpenVPN Cloud into the Single sign on URL Validator and ACS (Consumer) URL input field of Okta

      • Checkmark the Use this for Recipient URL and Destination URL option

      • Select EmailAddress as the Name ID format

      • Click on the Next button

    4. On the last page, select I’m an Okta customer adding an internal app and click on the Finish button.

    5. Click on the Sign On tab and click on the View Setup Instructions button

    6. The X.509 Certificate and the Identity Provider Single Sign-On URL will be needed later. Copy and paste this information for use later or keep this browser window open

    7. Now that OpenVPN Cloud has been setup as an application, you need to provide applicable users access to OpenVPN Cloud application. Click on the Assignment tab of the application and assign it to applicable users or select the user and assign the application.

    8. Okta will only provide the NameID value to the Service Provider by default which OpenVPN Cloud will map to the username of the User. If you want OpenVPN Cloud to have more information about the user and to use the value of a specific user attribute to map the user into an OpenVPN Cloud User Group, you need to configure parameters to be sent from Okta to App. See,

  3. Go back to the browser tab/window displaying the OpenVPN Cloud and take the following actions:

    1. Click on the Next button

    2. Provide an IdP Name, Select Manual Configuration, and do the following:

      • Paste the Identity Provider Single Sign-On URL value copied earlier in step ‘2.f’ into the IdP Authentication Endpoint

      • Paste the X.509 Certificate copied earlier in step ‘2.f’ into the IdP X.509 Public Certificate

    3. If earlier in step ‘2.h’ you had setup additional parameters to map into OpenVPN Cloud User information, do the following or else click on the Next button:

      1. Expand the Advanced settings section

      2. In the Attribute Mapping section provide the Identity Provider parameter names corresponding to the OpenVPN Cloud User information fields that you want to be populated with information from the Identity Provider’s parameters (SAML attributes) and click on the Next button when done

    4. Click on the Finish button after reviewing the SAML configuration

    5. Now that the SAML configuration is done, we need to enable SAML as the user authentication method by clicking on the Edit button in the User Authentication tab

    6. Select the SAML option

    7. If earlier in step ‘2.h’ you had setup an additional parameter with the intention to map the value of that parameter to OpenVPN Cloud User Group, do the following or else click on the Update Settings button:

      1. Click on the Add Rule button

      2. Enter in SAML IdP User Group(s) field one or more of the values that will present in the IDP provided parameter that you had mapped to the Group attribute in step ‘3.c.ii’and select the corresponding you want those values to map into. For example, the IdP user’s department value of ‘DEV’ could map to OpenVPN Cloud User Group ‘Dev’ which has been configured to provide access to resources for developers. Repeat the step to add more rules as desired and click on the Update Settings button when done

    8. Click the Confirm button on the confirmation dialog

    9. SAML is now enabled

Login to User Portal

Now that SAML is enabled for the VPN when a User wants to sign in to the User Portal to download Connect Client or manage devices etc., the user will sign in using SSO credentials. When the user visits the User Portal (for example, at, the user will see the Identity Provider’s login screen

On successful first authentication, the Administrator will see the user details show up in the administration portal.

In the screenshot above, you can see that the user1 has been added after SAML authentication because the Auth Source is shown as SAML.