Changing Client Certificate and Trusted CA for Management Interface
The following example shows how to change the client certificate and update the trusted CA for Management Interface using WebConf.
The new superuser certificate has to be issued from the same CA (MyCustomCA) that we will install for TLS authentication. First we have to provide the information about the certificate (MyUsername.pem) that will be used as superuser.
Open the WebConf Access tab:WebConf Access
Check the SubjectDN of the certificate using openssl.
Run the following command as 'user':
In the subject value, slashes / have to be replaced with commas (,)
In the section PKI Appliance Management Accounts, select clientcert, provide the following SubjectDN and click Add:
EJBCA is using org.bouncycastle.asn1.x500.style.BCStyle which interprets SN as serialNumber. We inherit this in org.cesecore.util.CeSecoreNameStyle (Legacy reasons). This means that you have to replace SN with SURNAME otherwise there is the danger of getting locked out.WebConf Access add a new client certificate for TLS authorization
In the section Trusted CAs for TLS client authentication , click Browse and select the MyCustomCA-chain.pem file.
The whole chain from the issuer CA of the client certificate up to the trusted RootCA is required.WebConf Upload the new trusted CA chain
Click Activate new CA certificate to allow TLS to update the new trust of CA.
Once the update is made, the new trusted configuration is used for authentication in the Management Interface.WebConf New configuration for Management Interface is in use