Axell Alvarado

Hello Tomas, I've tried with Chrome, Firefox and Edge. The CA certificate is installed. Also tried accesing the Public Web with port 8442 and 8080 and no problem there, the only issue is when accessing to the 8443. Will check the fixes and get back. UPDATE: Tried doing the steps in the link provided and nothing worked, i think the problem is in the wildfly, bu i can't see anything even with the log in debug level.

Hello Tomas, I've tried with Chrome, Firefox and Edge. The CA certificate is installed. Also tried accesing the Public Web with port 8442 and 8080 and no problem there, the only issue is when accessing to the 8443. Will check the fixes and get back.

Hello Tomas, Answering your questions: Did you configure the certificate profile in a custom way? A: No, the certificate uses the default profile. Invalid key usage for the certificate, possbly related to the key type you use. A: Key Usages are: Digital Signing, Non Repudiation, Key Encipherment. Extended key usage not being Client Authentication. A: EKUs are: Client Authentication and Secure Email. Using DSA instead of RSA or EC. A: Key is RSA 2048. I'm posting the admin certificate, if you find...

Hello team, I'm installing for first time the new version of EJBCA (7.10.0.2) on Wildfly 26, i followed all the steps and i can see the Public Web, but when i want to access to the Administration GUI and the browser requests my SuperAdmin Certificate, it seems the certificate is being rejected since i get a message that says the browser has not accepted the client certificate: ERR_BAD_SSL_CLIENT_AUTH_CERT. I tried with some browsers and the result is the same, i activated the debug log but i don't...

https://doc.primekey.com/ejbca/ejbca-release-information/ejbca-release-notes/ejbca-7-0-0-release-notes

Hello team, I'm installing for first time the new version of EJBCA (7.10.0.2) on Wildfly 26, i followed all the steps and i can see the Public Web, but when i want to access to the Administration GUI and the browser requests my SuperAdmin Certificate, it seems the certificate is being rejected since i get a message that says the browser has not accepted the client certificate: ERR_BAD_SSL_CLIENT_AUTH_CERT. I tried with some browsers and the result is the same, i activated the debug log but i don't...

Maybe because you're using Galleon, some dependencies are missing, i suggest you to try with Wildfly full EE

Hello, I'm trying to configure a Standalone OCSP Responder for my CA. This is what i've done until now: Imported the Root and Intermediate to my OCSP server. Created a Crypto Token and a Key for the OCSP Certificate. Created the OCSP Key Binding and generated the CSR. In the CA Server, i created a Certificate with Extended Key Usage OCSP Signing. Created an End Entity Profile and issued the OCSP Certificate using my generated CSR. On OCSP Server, imported the OCSP Certificate in the OCSP Key Binding...