ADD-ON

A managed certificate authority inside your RADIUSaaS portal

SCEPman as a Service adds a managed certificate authority to your RADIUSaaS instance. Your MDM enrolls devices over standard SCEP, Linux devices enroll through its API, RADIUSaaS authenticates them with what it issues, and there is no CA server, Key Vault or App Service for you to run.

  • Managed CA per instance
  • Intune, Jamf Pro, Active Directory
  • OCSP always on
  • Generally available since April 2026

How to add SCEPman as a Service

  • Talk to sales
    Talk to sales
    We add SCEPman as a Service to your license and set up a CA for your instance.
  • It appears in your portal
    It appears in your portal
    A SCEPman section appears next to your RADIUSaaS settings: status, issued certificates, manual requests, tasks and settings.
  • Enroll devices
    Enroll devices
    Enroll the root CA once, switch on the endpoints you need and point your MDM at the SCEP URL shown on the status page.
ENDPOINTS

The ways your devices can request a certificate

Each way a device can ask for a certificate is an endpoint you switch on, with its own certificate profile. A request has to pass at least one of them, which is how SCEPman checks that the device really exists and is managed.

  • Microsoft Intune

    Checks the device against Intune or Entra ID before issuing. Optionally, a certificate counts as valid only while Intune marks its device as compliant.

  • Jamf Pro

    Checks Apple devices against your Jamf Pro inventory, with a challenge for your Jamf SCEP profile.

  • Active Directory

    Checks computer and user accounts in your on-premises AD through an encrypted Kerberos keytab.

  • Domain controllers

    Issues the certificates domain controllers need for LDAPS and Kerberos PKINIT.

  • Static challenge

    For other MDMs, such as Addigy, Iru, Mosyle, SOTI MobiControl with their guides in the SCEPman documentation, and for appliances no MDM can enroll: a shared challenge password. Renewals can work without it, by proving possession of the current certificate.

  • Static challenge + Entra device check

    The same, but the device must also exist in Entra ID.

  • Enrollment REST API

    Your own tooling requests certificates over HTTPS, authenticated with a RADIUSaaS access token. Linux devices, managed by Intune or not, enroll over REST or EST and renew with their current certificate once you switch renewal on.

THE CA

A root CA under your own name

You enroll the root CA once and choose its subject name: the common name and organization every issued certificate will show as its issuer. The name is permanent, so the portal shows it to you for confirmation before anything is created. The root CA is valid for 7,300 days; issued certificates for up to 3,650 days, as your profile says. The CA key lives in a Key Vault we operate. If your compliance rules require it, keep it in your own Azure Key Vault instead, where SCEPman creates an RSA-4096 key; that choice can't be changed later.
  • Subject name confirmed before enrollment
  • Own Key Vault optional, tested before you enroll
  • Entra tenant connection by admin consent or your own app registration
Example data.
REVOCATION

The CA answers revocation checks itself

  • OCSP always on

    Revocation is answered live over OCSP by a dedicated responder certificate, for every certificate the CA issues. Disable a device in Entra ID or start a retire or wipe in Intune, and its certificate is reported as revoked without anyone revoking it.

  • CRL when you need it

    Switch on a signed revocation list for clients that don't speak OCSP. Its distribution point goes into every certificate issued from then on.

SERVER CERTIFICATE

Your RADIUS server certificate comes from the same CA

With SCEPman as a Service in the same portal, the connection between RADIUSaaS and SCEPman is already there. Pregenerate a server certificate to check your device profiles, then let RADIUSaaS take over: it requests the server certificate from your CA, activates it and renews it before it expires.
Example data.
COMPARED

SCEPman as a Service next to SCEPman Enterprise

The same SCEPman with the same features. What differs is where it runs and who runs it.

SCEPman as a Service and SCEPman Enterprise, row by row
TopicSCEPman as a ServiceSCEPman Enterprise
Where it runsInside your RADIUSaaS instance, run by glueckkanjaIn your own Azure subscription, run by you
CA keyIn a Key Vault we operate, or in your own Azure Key VaultIn your own Azure Key Vault
HostingNothing for you to hostApp Service and Key Vault on your Azure bill
How you buy itRADIUSaaS & SCEPman SaaS BundleRADIUSaaS & SCEPman Enterprise Bundle: RADIUSaaS plus a SCEPman Enterprise license
Intune, Jamf Pro and Active Directory enrollment✓✓
Automatic revocation from Entra ID and Intune✓✓
Intune compliance check✓✓
Linux over the REST and EST API✓✓
RADIUS server certificate renewed through SCEPman✓✓

Both editions run the same SCEPman code; hosting and the key store are what differ.

BUYING

RADIUSaaS and SCEPman as a Service in one subscription

Add the CA to your RADIUSaaS license

Tell us how many users you have, and we set up the CA for your instance.