What the protocols do
LDAP provides a standard way for applications and systems to query directory information. RADIUS handles authentication, authorisation and accounting for network access such as enterprise Wi-Fi or VPN services. They are often used together, with RADIUS validating a user against a directory.
Why I work with them
I use LDAP and RADIUS concepts in both workplace and lab contexts because centralised identity is more realistic than creating unrelated local accounts everywhere. In the home environment, the project supports learning how Wi-Fi authentication and service logon can be tied to controlled identities.
What I test
- Directory bind and search behaviour
- RADIUS clients and shared-secret handling
- Authentication success and failure logs
- Certificate trust for enterprise Wi-Fi
- Group-based access decisions
- Fallback and recovery when the identity service is unavailable
Product-name caution
I have not published a JumpCloud or CloudJump claim because the exact product name from earlier work still needs confirmation. This page documents the protocols and administration work I can state confidently.
Use certificates where supported, keep shared secrets private and confirm fallback access before changing the authentication path for a real network.
Deploy FreeRADIUS and an LDAP directory in an isolated lab, create test identities and configure a single access point or client to authenticate against them.