Skip to content

Version 10.1


This is an old version. We strongly recommend upgrading your appliance to the latest version to ensure optimal performance and security.

Upgrading to the latest version provides enhanced security features, bug fixes, and overall improvements, safeguarding your system against potential vulnerabilities.

Features & Improvements


Support for Google and Microsoft OATH tokens has been implemented. OATH tokens provide one-time passwords to end users and are a form of strong authentication.

The Initiative for Open Authentication (OATH) is a collaborative effort of IT industry leaders aimed at providing a reference architecture for universal strong authentication across all users and all devices over all networks. Using open standards, OATH will offer more hardware choices, lower cost of ownership, and allow customers to replace existing disparate and proprietary security systems whose complexity often leads to higher costs.

An OATH license is required for this feature.

Visit for additional information.


The AXS Guard documentation is constantly updated to reflect the various updates and improvements in the software and the product as a whole. Documents are available in the PDF and HTML format.

The following manuals have been updated:

  • AXS Guard Authentication Guide

The following articles have been added to the knowledge base:

  • How to set up your Google Authenticator

  • How to set up your Microsoft Authenticator


Microsoft and Google Authenticator Support

Both Google and Microsoft provide authenticators based on the OATH standard. Most implementations of OATH leverage smartphones and apps for the generation of one-time passwords.

The Authenticator apps can be downloaded from the Android and iOS app stores at no cost.


Tokens cannot be assigned without a valid license; a new system license is required. Contact your reseller to obtain an OATH token license.

Go to System > License > Authenticators > OATH to view your license details.


On the server side, secrets are provisioned by assigning a token to a user. An e-mail with configuration instructions is automatically sent to the user’s AXS Guard mailbox after a token has been assigned by an administrator.

On the client side, the user can simply import the secret by scanning the QR code provided in the e-mail, which also contains instructions to manually enter the required information.

Authentication Policies

New policies have been added to accommodate authentication with OATH tokens. These feature authentication methods for both password (PAP) and challenge (CHAP) based authentication protocols, as used by PPTP and L2TP VPN services.