Netscape MANAGEMENT SYSTEM 6.2 - ADMINISTRATOR Administrator's Manual page 416

CEP Enrollment
Setting Up Multiple CEP Services
This step is optional.
By default, the CEP service runs on this URL:
It is possible to set up multiple instances of CEP, each with a different
configuration, each listening on a different URL. This is useful if you have different
requirements for different types of users. For example, you might want to have one
CEP service that authenticates routers and publishes their certificates to the
directory and another CEP service that authenticates VPN clients but does not
publish their certificates to the directory.
To set up multiple CEP services, use the following example as a guide.
## Router configuration
eeGateway.cep.cep1.appendDN=O=*BASE_DN*
eeGateway.cep.cep1.createEntry=true
eeGateway.cep.cep1.entryObjectClass=cep
eeGateway.cep.cep1.url=/cgi-bin/pkiclient.exe
eeGateway.cep.cep1.authName=flatfile_router
## VPN configuration
eeGateway.cep.cep2.url=/vpnenroll
eeGateway.cep.cep2.authName=flatfile_VPN
## Router authentication parameters in the configuration file
auths.instance.flatfile_router.fileName=
auths.instance.flatfile_router.authAttributes=pwd
auths.instance.flatfile_router.keyAttributes=UNSTRUCTUREDNAME
auths.instance.flatfile_router.pluginName=flatfile
auths.instance.flatfile_router.deferOnFailure=true
## VPN authentication parameters in the configuration file
auths.instance.flatfile_VPN.fileName=
<full_path_to_the_authentication_file>
auths.instance.flatfile_VPN.authAttributes=pwd
auths.instance.flatfile_VPN.keyAttributes=CN,OU,O
auths.instance.flatfile_VPN.pluginName=flatfile
auths.instance.flatfile_VPN.deferOnFailure=false
## FlatFileAuth plugin registered in the configuration file
auths.impl.flatfile.class=com.netscape.certsrv.authentication.
FlatFileAuth
416 Netscape Certificate Management System Administrator's Guide • June 2003
<full_path_to_the_authentication_file>
/cgi-bin/pkiclient.exe