Self Service Role
Last updated
Last updated
Applicable to SCEPman version 2.9 and above
For clients to enrol certificates for themselves without SCEP, they can use the SCEPman REST API. However, they should not be able to enrol any arbitrary certificate, only certificates that are tied to their own identity. Therefore, the SCEPman API has a role that can be assigned to users/groups to enable this.
This role is included from SCEPman 2.9 onwards. If you installed SCEPman prior to this, you need to run the installation script again for this role to appear.
You can check that the Self Service role exists in the SCEPman-api App Registration:
You can create role assignments for users and groups in the SCEPman-api Enterprise Application.
A user with the self-service role can only enrol certificates with the following attributes. (These are the same as the attributes you would select when enrolling certificates via a SCEP profile in Intune for instance). The certificate's validity will be tied to the device object in Intune or Entra Id or to the user object in Entra Id, analogously to Intune-enrolled certificates.
Either the Subject Alternative Name (SAN) must include IntuneDeviceID://<IntuneDeviceId> as an URI, where <IntuneDeviceId> without the curly braces is the Device Id of the device in Intune. Or the CN field of the Subject must be the Entra ID device ID or the Intune Device Id. If you use the SAN method, you can have any kind of Subject, e.g. the name of the device (except for values that look like a Guid).
| Field | Value |
|---|---|
Subject |
|
SAN (URI) |
|
Basic Constraints |
|
EKUs |
|
| Field | Value |
|---|---|
Subject | No Restrictions, except the CN should not be a Guid. |
SAN (Other Name/UPN) |
|
Basic Constraints |
|
EKUs |
|
On Linux, follow the instructions of the Linux Enrollment Guide.
For other plattforms, follow our general instructions for using the Enrollment REST API.
