WiKID Strong Authentication System Java Token Client 3.1.23
Java Token for the WiKID Strong Authentication System
Fundamentally, WiKID Strong Authentication works this way: A user selects the WiKID domain they wish to use on their token client. The user is prompted for the PIN for that domain. It is encrypted with the WiKID Server's public key - assuring that only that server can decrypt it with its private key - and sent to the WIKID server. If the server can decrypt the PIN and it is correct and the account is active, it generates the one-time passcode (OTP) and encrypts it with the client's public key. The user then enters their username and the OTP into whatever service they are using, a VPN, website, etc., which forwards it to the WiKID Server for validation using Radius, TACACS+, LDAP or through our wAuth API for custom applications.
The WiKID Strong Authentication System is a key-based two-factor authentication system. It is a flexible, extensible, and secure alternative to tokens, certs and passwords. Application & API support exists for Java, ASP, PHP, OpenVPN, Ruby, TACACS+, etc.
The WiKID Strong Authentication System offers the features needed today to meet today's tough compliance standards and tomorrow's threats. Only WiKID can do two-factor session authentication, mutual https authentication to thwart man-in-the-middle attacks and is extensible to perform transaction authentication.
The WiKID Strong Authentication System is much less expensive than traditional hardware tokens. Hardware tokens are expensive, need to be inventoried and delivered. WiKID has focused on reducing the TCO of two-factor
WiKID Strong Authentication System Java Token Client
In a hurry? Add it to your Download Basket!
What's New in This Release:
- Signed with an updated JCE cert file.