RCDevs OpenOTP Radius Bridge provides a RADIUS RFC-2865 (Remote Authentication Dial-in User Service) API for the OpenOTP Authentication Server. It is an optional server component to be deployed on top of your OpenOTP infrastructure. Radius Bridge is implemented over the powerful FreeRADIUS software. The RADIUS API interfaces with VPN servers and many other software applications requiring end-user authentication. The supported authentication schemes are based on One-Time Passwords technologies (OATH HOTP/TOTP or mOTP Software Tokens, SMS One-Time Passwords, and Mail / Secure Mail One-Time Passwords).
Release Notes: This version is required with the OpenOTP v1.1.x branch. It supports the OpenOTP newer simpleLogin method and includes some fixes.
Release Notes: This release adds compatibility with OpenOTP 1.0.17 with location-based policies and some minor new features. It supports RADIUS accounting (RFC 2866).
Release Notes: A RADIUS Accounting service is now enabled on port 1813 and stores the accounting data in the logs/accounting.log file. A RADIUS Server Status service is now enabled on port 18120. Request attributes' encoding is checked for for username, password, and state attributes. Settings were added to disable the reply messages in success and failure responses for some broken RADIUS clients. The log file does not display user passwords.
Release Notes: Several bugs were fixed. It is now possible to return some RADIUS attributes set in the user ReplyData to the VPN server (per-user attributes). It is possible to return fixed RADIUS attributes too (common attributes). The password separator character is now configurable with concatenated LDAP+OTP mode.
Release Notes: The data_separator setting was added to allow returning multiple Reply Data. Support for OpenOTP 1.0.11-1 was added. An otp_length max limitation problem was fixed.