Certificates for everything Intune never sees.
Web servers, RADIUS servers, Linux hosts and build pipelines need certificates from the same root your devices trust. SCEPman gives them a portal with roles for the one-off request, a PowerShell module and a REST API for automation, and renewal over EST that needs nothing but the certificate the server already has.
- EST
- REST API
- PowerShell on Windows, macOS and Linux
- Certificate Master with roles
PS> Install-Module SCEPmanClientPS> New-SCEPmanCertificate -CertificateFromFile ./intranet.pem -KeyFromFile ./intranet.key -SaveToFolder ./certsRenewing CN=intranet.contoso.com over EST (simplereenroll) …Authenticated with the current certificate. No secret needed.New certificate saved to ./certs, valid for 365 days.
The right enrollment path for each system
Tell us what needs a certificate. We'll show you how it gets one and how it stays valid.
- How it gets the certificate
- The SCEPmanClient PowerShell module requests the certificate and stores it in the machine store.
- Who it proves itself to
- Entra ID, as a service principal or an admin with the right role.
- How it renews
- Over EST, signed with the current certificate, whenever your renewal job runs.
Request certificates by hand in Certificate Master
- Choose the lifetime of a certificate, within the maximum you set per type.
- Search the certificates SCEPman issued, whether through Intune, Jamf, EST, the API or the portal, and see whether one is valid right now, with the reason if it isn't.
- Revoke with one click; Certificate Master records who did it.
- Export the filtered list as CSV.
- Keys come as PKCS#12, PKCS#12 with legacy crypto for macOS and Windows Server 2016, or PEM with a password-protected key.
Renewal without a secret on the server
- Works from the SCEPmanClient module on Windows, macOS and Linux.
- Renewal is off until you switch it on for the endpoint that issued the certificate.
- The first certificate comes from an authenticated request: Entra ID, Certificate Master or the API.
Request certificates from scripts and pipelines
SCEPmanClient
A PowerShell module from the PowerShell Gallery for Windows PowerShell 5 and PowerShell 7 on Windows, macOS and Linux. Requests and renews certificates, stores them in the Windows certificate store, a folder or an Azure Key Vault.
Enrollment REST API
Send a CSR, get a certificate. Authenticated with Entra ID; an app role decides who may call it. You can fix the extended key usages the API hands out.
Management REST API
New in 3.1: search issued certificates and revoke them from a script, with Entra authentication and its own role. Enterprise Edition. The SCEPmanClient module has cmdlets for both.
Users and devices that enroll themselves
Questions about server certificates
01Are these certificates trusted by browsers on the internet?
No. SCEPman is your private CA, so its certificates are trusted where you deploy the root: your managed devices and servers. For a public website, use a public CA.
02Can a server renew forever without a person?
Yes, with EST. Each renewal proves itself with the current certificate. If a certificate expires before it is renewed, the next one needs an authenticated request again.
03Which key sizes are possible?
Through a CSR, whatever the requester generated. In the Certificate Master form, RSA 2048 or 4096 bits.
04Who sees what in Certificate Master?
Roles in the Certificate Master app registration decide it, per certificate type and per method. A helpdesk group can be allowed server certificates by CSR and nothing else.
05Do server certificates count as licensed users?
Users who connect to services secured with SCEPman server certificates count. In practice that is often everyone who has the SCEPman root on a device.
06Can SCEPman issue the certificates for Remote Desktop?
Yes. Domain-joined servers can get an RDP certificate through group policy autoenrollment from the Active Directory endpoint of Enterprise Edition, and other servers request one in Certificate Master or over the REST API. Remote Desktop clients then trust the server through your root instead of the self-signed certificate Windows creates.
07Can SCEPman issue certificates for routers, switches and access points?
Yes. Request a device certificate in Certificate Master, either with a key Certificate Master creates (RSA 2048 or 4096 bits, as PKCS#12 and PEM) or from a CSR the device generated, and install it on the device. A role decides who may request one.
One root for devices and servers.
Start with the first server certificate in Certificate Master, then automate the renewals.