Skip to main content
USE CASE · NETWORK ACCESS

Wi-Fi, LAN and VPN that know when a device is gone.

Your MDM puts a certificate on every laptop and phone. The RADIUS server or VPN gateway checks it at every connection, and SCEPman answers from Entra ID, Intune or Jamf. A device you delete there loses network access at the next check, with nobody editing a revocation list.

  • EAP-TLS
  • OCSP check at every login
  • No password crosses the network
Example data.
THE CASE

Certificates keep passwords off the RADIUS server

With password-based Wi-Fi authentication, the user's credentials, or something derived from them, end up at the RADIUS server, and you never want Entra ID passwords anywhere but Entra ID. A certificate proves the device or user without sending a secret: the private key never leaves the device.
  • Device certificates sit in the machine store, so the laptop joins the corporate Wi-Fi before anyone logs on.
  • Nobody types anything. The Wi-Fi profile and the certificate arrive together from the MDM.
  • A certificate belongs to one device or one user, so access ends with that object, not with a shared password everyone knows.
AFTER DAY ONE

How certificates are issued, renewed and revoked

Three things happen without a ticket.

  • Issue

    A new device enrolls in Intune or Jamf and receives its SCEP profile. SCEPman issues the certificate after Intune or Jamf vouches for the request.

  • Renew

    The MDM renews the certificate before it expires, on the threshold you set in the profile. SCEPman caps every certificate at the maximum you configure, 365 days for Intune by default.

  • Revoke

    Delete or disable the device or user, or wipe the device in Intune. SCEPman answers "revoked" or "on hold" at the next check. Optional in Enterprise Edition: devices that fall out of compliance and users whose risk level rises.

What happens in your tenant

Device certificateNB-MUC-0412

SCEPman answersGood

Reason
Device found and enabled
A client that cached the last answer sees this within
nothing changes
This answer may be cached for
10 minutes
Can be undone
Not needed

Numbers are SCEPman's defaults; you can shorten them. Example data.

COMPATIBILITY

Network services customers use with SCEPman

Anything that does EAP-TLS and checks revocation over OCSP works with SCEPman certificates. These are the services our customers run most often.

Network services customers commonly use with SCEPman certificates
ServiceTypical use
RADIUSaaSWi-Fi, LAN and VPN
Aruba ClearPassWi-Fi and LAN
Cisco ISE and Cisco ASAWi-Fi, LAN, VPN
Azure VPN Gateway and Always On VPNVPN
Fortinet FortiGateVPN and Wi-Fi
Palo Alto GlobalProtectVPN

Kiosk systems, self-checkouts and barcode scanners get device certificates the same way, which is how many customers bring them onto the corporate network.

FIREWALLS

A sub CA for TLS inspection

Firewalls that inspect TLS need their own CA certificate that your clients trust. Certificate Master issues sub CA certificates under your SCEPman root for Azure Firewall Premium, Microsoft Entra Internet Access and other appliances. The devices that already trust SCEPman trust the firewall's certificates without another root deployment.
BETTER TOGETHER

A cloud RADIUS server from the same team

RADIUSaaS is glueckkanja's RADIUS service in the cloud. It validates the certificates SCEPman issues, and with SCEPman Connection it gets its own server certificate from SCEPman and renews it the same way. Both products come from one team, as a bundle 25% below the two bought separately.

Questions about network access

01Does the laptop need a user logged on to join the Wi-Fi?

No. A device certificate is available to Windows before logon, so the network is there for the logon itself.

02How fast does a deleted device lose access?

Immediately: SCEPman answers "revoked" from the moment the device is gone. A RADIUS server that caches OCSP answers may keep the last "good" for up to 10 minutes by default; you can shorten that.

03What if SCEPman is unreachable?
Then the RADIUS server can't get a fresh answer and follows its own policy for failed revocation checks. If you need SCEPman to stay reachable when an Azure region fails, Enterprise Edition lets you add a second instance in another region. A default installation runs in one. In the SaaS Bundle with RADIUSaaS, we run SCEPman for you, and keeping it reachable is our job: compare the two bundles.
04Can we use user certificates instead of device certificates?

Partly. SCEPman checks the user in Entra ID: disabled means on hold, deleted means revoked. A user certificate is only there once someone has signed in, so a Windows PC with nothing but a user certificate stays off the network at the sign-in screen, and signing in may need that network. On Windows, use device certificates, or chain the two: the device authenticates first, and once the user has signed in, it authenticates again with the user certificate. Chaining doesn't work on shared devices.

05Does SCEPman fit a Zero Trust design?

Yes. A certificate proves the device or user at every connection, and the answer to the revocation check comes from Entra ID, Intune or Jamf, so access follows the state of the device rather than its place on the network. With the compliance check of Enterprise Edition, it also follows Intune compliance.

Put certificates on your Wi-Fi.

Deploy SCEPman, assign a SCEP and a Wi-Fi profile, and point your RADIUS server at the root.