Use Microsoft Entra ID credentials to protect applications, admin portals, network appliances, and internal systems that still rely on LDAP or RADIUS. Rublon Authentication Proxy lets these systems keep their existing authentication protocol while Microsoft Entra ID verifies primary credentials and Rublon MFA adds an extra layer of access protection.
Scenario
Your organization uses Microsoft Entra ID for identity management, but some applications, admin portals, network appliances, or internal systems still support only LDAP or RADIUS authentication.
These systems may be critical to daily operations, but they were not designed for modern identity protocols. They cannot connect directly to Microsoft Entra ID through SAML, OAuth 2.0, or OpenID Connect, and replacing them may be expensive, risky, or unrealistic in the short term.
Challenge
Microsoft Entra ID is not a traditional LDAP directory or a native RADIUS server. This means LDAP and RADIUS VPNs and applications cannot authenticate directly against Microsoft Entra ID.
As a result, organizations often keep local Active Directory, LDAP directories, RADIUS servers, service accounts, and related infrastructure only because a few important systems still require LDAP or RADIUS. This creates duplicate identity infrastructure and makes it harder to standardize authentication around Microsoft Entra ID.
Solution
Rublon Authentication Proxy provides a compatibility layer between LDAP and RADIUS applications and Microsoft Entra ID.
The protected application continues to use LDAP or RADIUS. Rublon Authentication Proxy receives the authentication request, verifies the user’s primary credentials against Microsoft Entra ID, and then requires Rublon MFA before access is granted.
This allows users to sign in to LDAP and RADIUS applications with Microsoft Entra ID credentials, even when those applications do not support Microsoft Entra ID natively.
Benefits
- Use Microsoft Entra ID credentials for LDAP and RADIUS applications.
- Add Rublon MFA to applications that do not support modern identity protocols.
- Keep legacy applications working without rewriting or replacing them.
- Reduce dependency on separate LDAP or RADIUS identity sources.
- Standardize primary authentication around Microsoft Entra ID.
- Protect access to legacy apps, admin portals, network appliances, and internal systems.
- Support cloud-first identity projects while preserving access to business-critical systems.