FAQ: Twingate Migration for ODBC / SDK Customers

Introduction

In order to comply with security best practices, Texada is requiring all current OpenVPN customers to transition to Twingate by December 15th, 2024. This change will involve downloading the Twingate client, joining the Texada network, and setting up multi-factor authentication (MFA) to access Texada resources.

Frequently-Asked Questions

Who does this impact?

All Texada customers using ODBC or SDK will be impacted by this change.

Why does this need to be completed?

Our current OpenVPN connection method does not meet Texada’s current security posture.. It lacks multi-factor authentication (MFA), which is now a common requirement for insurance policies and security certifications. As always, we want to ensure we have the best, most secure product available. As such, we will be improving our security by leveraging Zero Trust Networking. This exceeds best practices and provides the best experience for our customers.

When does this need to be done by?

Affected customers must transition from OpenVPN to Twingate by December 15th, 2024.

What will happen if we don’t complete the transition?

If the transition to Twingate is not completed by the deadline, OpenVPN services will be disabled, preventing access to ODBC or SDK services utilizing internal ports.

How will my user experience be impacted?

The connection process for Twingate is similar to that of OpenVPN; however, there will be no need to manage profiles or different VPN profiles. The major change will be the requirement to use MFA.

How do I complete the installation?

Click the button below for detailed instructions on setting up the Twingate client.