Release Notes: A JSON Web API was added. SMTP support was added. A WSDL namespace issue when imported in VisualStudio .NET was corrected. TOKEN, LIST, and LASTOTP fallback methods are now allowed with any OTPType. The fallback is automatically disabled if the user data are missing. SMS and Mail OTP support prefetched delivery mode (next OTP is send after authentication). LASTOTP has an expiration time. Major code rewrites, optimizations, and OTP fallback changes were made.
Release Notes: This release contains many fixes and new features. It supports expired passwords detection, SafeNet Tokens, additional APIs, OTP PIN codes, Token import via serial numbers, and more.
Release Notes: This major release includes several important new features, including support for multiple Tokens per user, new OTP fallback methods, a new simpleLogin API, and a new RadiusBridge.
Release Notes: This release adds support for geolocalization and IP location-based policies, adds a new XML-RPC API, improves logging, and fixes OCRA Tokens.
Release Notes: SMSOTP and MailOTP support for sending OTPs to several numbers/addresses per-user. MailOTP subject can be customized. The user blocking management was enhanced. Blocking alerts were added. An HOTP resync problem was fixed. A PSKC export problem was fixed. New requests are optionally allowed when a session is already started after a delay of 5 seconds (the existing session is dropped the and user does not have to wait for the challenge timeout). A 'Service Name' setting was added for customizing the Google Authenticator display name. A Manager function was added for checking user blocking status.
Release Notes: This version is fully compliant with WebADM 1.2 and supports the new WebADM Manager Interface. A JSON-RPC interface was added for the OpenOTP authentication API. SMS OTP supports concatenated SMS for messages longer than 140 chars. A HOTP manual resync issue was fixed. New requests are now allowed when a session exists after a delay of 10 seconds. The existing session is dropped and the user does not have to wait for the challenge timeout to expire.