JumpCloud identity and network authentication

Interface reference

What JumpCloud is

JumpCloud is a cloud directory platform used for identity, authentication and device access. In the context I worked with it, the important parts were user authentication, LDAP-style directory access and RADIUS-backed network logon for services such as Wi-Fi.

What I did at ITHQ

I used JumpCloud at ITHQ for authentication with users, Wi-Fi access and related LDAP/RADIUS workflows. The work sat alongside wider managed-service activity, where secure login and controlled access were part of supporting business systems.

My focus was understanding how users, devices and network access fit together: the identity source, the authentication protocol, the network device or wireless access point, and the trust boundary between them.

Identity and network access

JumpCloud helped connect cloud identity to network access requirements. That included understanding how RADIUS can authenticate Wi-Fi, VPNs, switches and network devices, and how LDAP can expose directory authentication to systems that require it.

This links directly to my separate LDAP and RADIUS authentication page, because the useful skill is not only knowing the product name, but understanding what problem the protocols solve.

How to deploy or reproduce it

Representative lab flow only — do not publish real secrets, shared keys or production IP addresses.

1. Create a test user or group in a JumpCloud test organisation.
2. Enable LDAP or RADIUS access only for the users/groups that need it.
3. For RADIUS, create a server profile, set a strong shared secret and restrict allowed source addresses.
4. Point a lab wireless access point, router or VPN service at the RADIUS endpoint.
5. Test authentication, failed-login handling, group policy and offboarding.
6. Document how access is removed when a user leaves or a device is no longer trusted.

In a real environment, use MFA where supported, least privilege, controlled admin roles and clear onboarding/offboarding procedures.