When access adminweb EJBCA "No client certificate was presented"

[alandrma]

Hi everyone,
I want to ask regarding accessing the ejbca web admin.

i have deployed ejbca v8 with wildfly 26.
using mariadb with connector version 2.7.0

When the process of deploying and importing the superadmin certificate that has been generated by EJBCA has been completed into Firefox, it still doesn't work. there is an error as follows.

and when I checked the certificate in Firefox when accessing adminweb, Firefox didn't detect the superadmin that had been imported previously. In fact, the certificate in Firefox is detected as localhost cert, not superadmin which was previously generated. Please help, do you think there are any wrong steps? Thank You

Edited : I was using RSA 2048 with management CA

[primetomas]

If you can't see the client certificate, looking in the right place, in FireFox it wasn't installed.
Are you accessing wildfly on port 8443? If the superadmin.p12 (not only a certificate, but the p12 with the private key as well) was imported you should be prompted to select the certificate.

Firefox->Settings->Privacy&security->View certificates->Your certificates.

[primetomas]

Yeah, you need to follow the installation instructions all the way through the end.
https://doc.primekey.com/ejbca/ejbca-installation, which includes TLS setup with the server certificate generated.

[gilles380]

hi @primetomas
I need some clarification on how I can modify install.properties AFTER I have my ejbca running.
As told in the documentation, it is not needed to recompile right ? (just restart WildFly server ?)
Because, I tried to access with REST API with Curl from an external host and it come with :
curl: (60) SSL: no alternative certificate subject name matches target host name '192.168.x.y'
Also , external web access to ejbca admin GUI does not work either,
What would be your recommendation to have external access working (I dot not have any apache proxy, just my local network as it is)
thanks for your support

[primetomas]

install.properties is completely useless after you have done the first installation.

What you can do is that you can re-issue the TLS server certificate by editing the end entity 'tomcat' and setting other values for dnsName.
https://doc.primekey.com/ejbca/ejbca-operations/ejbca-operations-guide/ca-operations-guide/end-entities/ssl-certificate-expiration

[merryo11]

What if we change the local SSL under management CA with commercial CA SSL like under digicert, sectigo or let's encrypt

[primetomas]

Then you will simply use those keystores in your WildFly/JBoss installation instead of ones generated by EJBCA. These are simply jks/p12 keystore files copied to a WildFly directory. You can use any keys/certificates you like for TLS in WildFly.