This article provides installation requirements and interoperability data for Nexus Hybrid Access Gateway.
Nexus Hybrid Access Gateway comes as a virtual appliance and boasts simplified administration with easier deployments, upgrades and maintenance.
This article contains requirements and interoperability details for the setup and the different parts of Hybrid Access Gateway.
* For proof of concept and testing VMware Fusion, VMware Workstation/Server or VirtualBox can be used.
** For proof of concept and testing Hyper-V running on desktops can be used.
Hybrid Access Gateway stores its user representation in a database, the appliance comes with a built-in database (PostgreSQL). That means there are no requirements for external databases to get started. To read more about external database, see Database service.
The following databases has been explicitly verified:
Hybrid Access Gateway can link to existing users stored in a directory (LDAP). The virtual appliance is fully LDAP v3 compliant for connecting to these user storages.
The following directories has been explicitly verified:
To use stronger crypto functions the Unlimited Strength Jurisdiction Policy Files need to be downloaded manually and the old ones replaced.
Make sure to have the same rights on the new files as the old ones.
The following browsers are supported for the portal, administrator, federation, and web authentication:
The following operating systems are supported for TruID:
The following operating systems are supported for the Access client:
The following browsers are supported for the access client:
This section contains details on the AccessNow compatibility for server client and target system.
Supported target server OS
Supported target client OS
Supported client browsers
This article is valid for Hybrid Access Gateway 5.13