Version 4 is the product that evolved as the Version 3 as it should have been written. Long experience with RADIUS and suggestions by developers have lead to the rewriting of the new version.

Much of the code in V3 was transferred to V4 since something that has worked for 15+ years should be retained. The API has changed the most for the better with more packages isolating a crowded base package.

Version 4 introduces a much more secure internal structure by wiping sensitive data values before releasing them to the garbage collector preventing quite a number of problems in other systems.

EAP is well supported in both the client and server. The client’s EAP configuration is minimal – merely configuring the EAP methods and then calling the authentication method.

Server side EAP is not so straight forward so the API uses callbacks at appropriate times during the EAP authentication.

The future for Version 4 is to continue expanding the number of EAP authentication methods as well as continue to incorporate many of the RADIUS RFC’s as they become more popular.

The ‘best practices’ style RFC’s are frequently examined and incorporated unless they pertain to policy best handled by the developers.

Currently we are developing TLS support for 1.1 and 1.2. TLS 1.3 is still in it’s draft phase.