OpenVPN with SAML Client on Okta IDP

1. Overview

Aviatrix user VPN is the only OpenVPN based remote VPN solution that provides a vpn client that supports SAML authentication.

This guide provides an example on how to use Aviatrix SAML client to authenticate Okta IDP. When SAML client is used, Aviatrix controller acts as the identity service provider (ISP) that redirects browser traffic from client to IDP, in this case, Okta, for authentication.

2. Pre-Deployment Checklist

Before configuring the SAML integration between Aviatrix and Okta, make sure the following is completed.

Pre Installation Check List

  1. Aviatrix Controller is setup and running.
  2. Have a valid Okta account with admin access.
  3. Download and install the Aviatrix SAML client These prerequisites are explained in detail below.

2.1 Aviatrix Controller

If you haven’t already deployed the Aviatrix controller, follow the below instructions on how to deploy the Aviatrix controller. Instructions here.

2.2 Okta Account

A valid Okta account with admin access is required to configure the integration. If you don’t already have an Okta account, please create one with the following link from Okta. Okta create account

2.3 Aviatrix SAML Client

All users must use the Aviatrix SAML client to connect to the system. Download the client for your OS here.

For Linux users, do this::

tar -xvzf AVPNC_linux.tar.gz;
cd AVPNC_setup;

to install type AVPNC in the terminal to run.

3. Configuration

The integration configuration consists of 4 parts.

  1. Create an Okta SAML App for Aviatrix
  2. Retrieve OKta IDP metadata
  3. Launch Aviatrix Gateway
  4. Create Aviatrix SAML SP

Please complete the configuration in the following order.

3.1 Create an Okta SAML App for Aviatrix

This step is usually done by the Okta Admin.

  1. Login to the Okta Admin portal
  2. Click “Admin”
  3. Click “Applications”
  4. Click “Add Application”
  5. Click “Create New App”
    1. Platform = Web
    2. Sign on method = SAML 2.0


  1. General Settings
    1. App Name = Aviatrix Dev (arbitrary)


  1. SAML Settings
    1. Single sign on URL* = https://aviatrix_controller_hostname/flask/saml/sso/aviatrix_username
    2. Audience URI(Entity ID)* = https://aviatrix_controller_hostname/
    3. Default RelayState* =
    4. Name ID format = Unspecified
    5. Application username = Okta username

    These values are also available in the controller OpenVPN->Users page after step 3.4


    The aviatrix_controller_hostname is the hostname of the Aviatrix controller(If no DNS is used, this is the public IP). The aviatrix_username is an arbitrary identifier. Note this value as it will be needed when configuring SAML from the Aviatrix controller. Please contact your Aviatrix admin if you do not have the Aviatrix controller’s public IP address.

    1. Attribute Statements
      1. FirstName -> Unspecified -> ${user.firstName}
      2. LastName -> Unspecified -> ${user.lastName}
      3. Email -> Unspecified ->


  1. Done

3.2 Retrieve Okta IDP metadata

This step is usually completed by the Okta admin.

After the above application is created, click on “Sign On” and then “View Setup Instructions”.


Look for the section titled “IDP metadata to your SP provider”.

image5 Note this information. This information will be used to configure the SAML configuration on the Aviatrix controller.

3.3 Launch Aviatrix Gateway

This step is usually completed by the Aviatrix admin.

  1. Login to the Aviatrix controller
  2. Click Gateway -> Add New
  3. Select the appropriate Account, region, vpc, subnet and gateway size
  4. Check “VPN Access” and then “Enable SAML”


  1. Default settings for everything else.
  2. Click “OK” to launch the gateway.

3.4 Create Aviatrix SAML SP

This step is usually completed by the Aviatrix admin.

  1. Login to the Aviatrix Controller
  2. Click OpenVPN -> VPN Users -> Add New
  3. Select the VPC where the above gateway was launched
  4. Username = aviatrix_username (this is the username that you choose during the Okta SAML configuration)
  5. User Email = any valid email address (this is where the cert file will be sent
  6. IPD Metadata type = Text
  7. IDP Metadata Text = paste in the IDP metadata from the Okta configuration
  8. Entity ID = Hostname


  1. Done