SCEP Server

The scep functionality is included as a special service with the core distribution and enabled by default. You can turn it off in the global system configuration (system.server.service).

The communication with your scep clients requires the deployment of a cgi wrapper script with your webserver. The script will parse the HTTP related parts and pass the data to the openxpki daemon and vice versa.

Wrapper Configuration

The default wrapper looks for its config file at /etc/openxpki/scep/default.conf. The config uses plain ini format, a default is deployed by the package:

log_config = /etc/openxpki/scep/log.conf
log_facility = client.scep




Described in the common wrapper documentation (Wrapper Configuration).


The realm of the ca to be used.


Implements a simple ip based access control, the clients ip adress is checked to be included in the given network. Only a single network definition is supported, the default of allows all ips to connect.


The default profile of the certificate to be requested, note that depending on the backing workflow this might be ignored or overridden by other paramters.


Path to the server side config of this scep service. Equal to the key from the config section in the scep.yaml file.


Encrpytion to use, supported values are I<DES> and I<3DES>.

Config Path Expansion

Is supported by the SCEP wrapper, the service name is scep. See the common wrapper documentation (Wrapper Configuration) for details.


The scep standard is not exact about the use of HTTP/1.1 features. We saw a lot of clients which where sending plain HTTP/1.0 requests which is not compatible with name based virtual hosting!

Please do NOT use SCEP over HTTPS, SCEP transport is protected on the application layer by default.