X.509 Certificate Properties




<list of provider names>

List of CA (Certificate Authorization) providers, each provider has a number of properties on it,



<list of public certificate files>

A public ceritificate is stored in a public certificate bundle in the format of a p7b file. This property defines all the public certificates of the CA's that's supported by the PortalProtect system.

tdc_prod.p7b, tdc_preprod.p7b


<java class>

Classname of the provider – the class must extend the class dk.itp.security.authentication.x509.CA. It contains the name of the root CA, as well as code for mapping between certificates and CPR/ID codes, if supported by the CA.
A special generic CA implementation ca be used to define basic CA functionality. The generic CA is defined using the following class:


Using the generic CA, the ca.provider.xxxx.issuerdn property must be defined.

For NemID, this should be set to


Issuer's DN

This property is only required if the GenericCA provider implementation is used, see property "ca.provider.xxxx.class" for more information on the GenericCA implementation.




URL to the place where the Certificate Revocation List can be retrieved.


<true | false> - Defaults to true

If true, the URL for the CRL lists embedded in the certificate will be used. If no URL is embedded in the certificate extensions, then the configured URL will be used.
Note that this value MUST be true for OCES II certificates since they are issued by different intermediate CA certificates and thus have different CRLs.


<interval in minutes> (default 15)

Define the number of minutes between trying to update the CRL list by re-retrieving it from the server.


<true | false>

If true, checks the X.509 extended key usage within the certificate, to make sure the certificate can be used to sign data with.


<true | false>

If true, the certificate will be checked against the CRL list to make sure it is not revoked.


<true | false>

If true, the X.509 certificate chain will be checked, to verify that each certificate is properly signed by the parent certificate.

ca.provider.xxxx. allow.obsolete.crl

<true | false>

If true, logins will be allowed even if the CRL is obsolete, if false logins will not be allowed if the CRL is too old. (default is false)


<true | false> (default true)

Specifies if the signature on the CRL should be verified against the issuer certificate – should only be disabled to guard against a bug in the CRL provider if they do not sign the CRL with the correct certificate, which should be the same one used to issue the users certificate which is checked against the CRL itself.


<true | false>

If true, the OCSP (Online Certificate Status Protocol) will be used to check a certificates validity – this as a good alternative to a CRL list, since the online check will immediately detect if a certificate is revoked without any time delay. Remember to set the URL too.

Default is false.



The URL to use when checking if certificates are revoked using the OCSP protocol.

Example: http://ocsp.certifikat.dk/ocsp/status


<true | false> - Defaults to true

If true, do not use the ca.provider.xxxx.ocsp.url configured, but prefer the URL embedded in the certificate – if no URL is embedded in the certificate the configured one will be used.
This value MUST be true for OCES II certificates.


<true | false>

If true, the timestamp on the response from the OCSP server will be ignored – otherwise it has to be between now – 2 minutes and now + 2 minutes. If your server timestamp is different from the OCSP servers timestamp this can cause problems, so in that case set this flag to disable the time checks.

Default is false.


<timeout in minutes>

Caches the certificates that have been checked via OCSP for the configured number of minutes. If they certificates login again with xxx minutes, they won't be rechecked to speed login up.

Set it to 0 to disable the cache.

Default is 5 minutes.


<Time difference in minutes> (Default 2)

Specifies the maximum time difference allowed between the current time and the time in the OCSP response.



ZZ is replaced with the nemID provider ID.

Name of the file the keystore is stored in (unless the key is stored in hardware)


<keystore type> - Default "PKCS12"

ZZ is replaced with the nemID provider ID.

Type of keystore, e.g. PKCS12, JKS or LUNA



ZZ is replaced with the nemID provider ID.

Password to keystore used for NemID applet parameter signing - can optionally be encoded or encrypted using "java dk.itp.utils.PasswordUtils".


Name of JCE provider to use when loading the keystore – default is BC

ZZ is replaced with the nemID provider ID.


<private key alias name>

ZZ is replaced with the nemID provider ID.

Alias name of the private key within the keystore to use when signing.

If not specified, the first available private key in the keystore will be used.


<certificate alias name>

ZZ is replaced with the nemID provider ID.

Alias name of the certificate to use when signing the applet parameters – the certificate will be included in the signed parameters, and must be known prior to NemID / DanID. Usually this will have to be an FOCES or VOCES certificate.

If not specified, the first available certificate in they keystore will be used.


<provider name> - Default BC

ZZ is replaced with the nemID provider ID.

Name of JCE provider to use, e.g. BC for BouncyCastle, SUN for Sun JKS keystores, LunaJCAProvider for Luna SA HSM.

The JCE provider specified will be used for signing the applet parameters, and can in some cases be different from the keystore JCE provider, but will usually be the same.


<List of integers, separated by , or ;> - Must be present when using NemID – you get the ID from DanID.

Each provider ID is used in the name of the appletparam* parameters to allow multiple applet signing certificates, each with its own company name which will be shown in the NemID applet.

List of DanID / NemID's service provider IDs.



Specify the name of the keystore containing an SSL client certificate for use with DanID PIDCPR lookup service.


<Keystore type> - Default PKCS12

Specify the keystore type.


<JCE provider name> - Default BC

Set the name of the JCE keystore provider used to load the keystore.


<Password for keystore>

Specify the password to open the keystore – note that the password can be obfuscated or encrypted with PasswordUtils.


<Alias name>

If specified, this is the alias in the keystore where the private key is stored – if not specified, the SSL JCE Provider will select a private key to use from the keystore.


<Alias name>

If provided, the alias of the public certificate within the keystore – if not specified, the SSL JCE Provide rwill select a certificate to use from the keystore.


<true | false> - Default true

If set to false, SSL hostname verification will be turned off, this means that PortalProtect will not verify that the SSL certificate contains the correct hostname for PID lookups, DanID Attribute service lookups, CRL lookups and OCSP lookups.

You should only set this to false if required for testing, never in production.



URL To TDC/DanID's attribute lookup service – e.g. https://test.lra.certifikat.tdc.dk/attributews/AttributeService or https://ws-erhverv.pp.certifikat.dk/attributeservice_serviceprovider_server/

This attribute service is used for looking up user attributes for MOCES certificates.


<true or false - default is true>

Set to false to disable verification of SSL server certificate


<List of filenames, separated by comma or semicolon>

List of trusted CA certificates for the SSL server certificates, if JRE's cacerts is not enough.


<JCE provider name> - Default "BC"
<Keystore type> - Default "PKCS12"
<Keystore filename>

These settings provide the keystore used as client certificate when contacting the attribute service.


<Issuer name> - Default "TDC OCES CA"

Name of issuer to put in the attribute service request – some services/environments might require different issuer names. The "Digital signatur" attribute does not care what the issuer name is set to. Others, like "NemID Erhverv" might require specific issuer names.



URL to the PIDCPR lookup service at DanID/Nets


<true or false - default is true>

Set to false to disable verification of SSL server certificate


<List of filenames, separated by comma or semicolon>

List of trusted CA certificates for the SSL server certificates, if JRE's cacerts is not enough.


<SSL Context provider name> - Default is blank (use JDK default)

Name of SSL provider to use when doing PIDCPR lookups.


<SSL protocol – default TLS>

Specify the SSL protocol to use for PIDCPR lookups – e.g. "TLSv1.2"


<true | false>

If true, the properties http.proxyHost, http.proxyPort, http.proxyUser and http.proxyPassword will be used when retrieving CRLs.


<ip address or hostname>

Address of the proxy server to use for HTTP and HTTPS URLs.


<port number>

TCP Port of the proxy server to use for HTTP and HTTPS URLs.


<userid> - default blank.

If not empty, the userid and corresponding password from http.proxyPassword will be used to add Proxy-Authorization header to the HTTP request to authenticate the request with the proxy server.



Password to add to the Proxy-Authorization header to authenticate to the proxy.



IPs / hostnames matching this pattern will bypass the proxy


<Comma separated list of LDAP servers>

The list of LDAP servers that contain listing of OCES public certificates – they are used from TDCOCESCertLookup which is able to lookup public OCES certificates in the LDAP servers based on serial number, email address or name.

Default is: "dir.certifikat.dk:389" which is the LDAP server for TDC OCES certificates.


<Base DN>

Base DN of the LDAP tree to search for public OCES certificates in – should not be changed from the default value for TDC OCES certificates.

Default is: "c=DK"


<Comma or semicolon separated list of classes>

This property is used to load support for custom JCE providers that require specific non-JCE initialization. It must contain names of classes which implement the interface dk.itp.security.jce.ICustomJCESupport interface.

Currently only one JCE provider which requires this custom initialization is supported, and that is the Luna Hardware Security Module (HSM).


It requires the following configuration property: luna.password which must be set to the password to log into the HSM.

Also, luna.provideroffset can be used to specify the index in the JCE provider chain to install the provider at – if nothing else is specified, 2 is assumed. Set it to -1 to add the provider at the end of the chain.


© Ceptor ApS. All Rights Reserved.