Passlogix Home
Request More Information about Passlogix

Universal Authentication Manager

Many organizations want to deploy stronger two-factor authentication for Windows logon to improve security and support regulatory compliance efforts, but are deterred by the cost and complexity of most solutions that often times locks-them into a single form of strong authentication. v-GO Universal Authentication Manager (v-GO UAM) eliminates these concerns with an open architecture that supports any authentication device, use of the organization’s existing back-end network infrastructure, and easy end user logon.

v-GO Universal Authentication Manager quickly and securely authenticates users to the Windows network (and, optionally, to v-GO Single Sign-On) with any authentication device from any vendor. Organizations that are already using building access badges, government-issued citizen identity cards, OTP tokens or laptop biometric readers can now use those same devices – or any combination - for Windows logon. Organizations without existing strong authentication technology can choose the best device or devices for their environment with assurance that they can be used for network access.

How it Works

To authenticate to Windows with v-GO Universal Authentication Manager, a user simply presents their authentication device to the workstation and v-GO Universal Authentication Manager does the rest. For example, a user who has a door access badge simply taps the badge on a badge reader attached to their computer and enters a PIN code. v-GO Universal Authentication Manager retrieves the user’s logon credentials from Microsoft Active Directory and compares them on the client. If they match, v-GO Universal Authentication Manager provides Windows with the information needed to log that user on. Another tap of the badge locks the workstation or logs the user off.

The use of Microsoft Active Directory for data storage and administrative policies eliminates the need for proprietary authentication servers. This lowers costs as well as avoiding the administrative overhead associated with managing a separate strong authentication infrastructure.