Basic authentication after client certificate failure when attempting to access the EJBCA administrator interface.

[erlispaula-coder]

Hello, I am attempting to restore EJBCA CE 7.11.0 on an EC2 instance running Ubuntu. I am using WildFly version 25.0.0. The issue I am encountering is that, once I have completed the entire setup process, I am able to access the web interface via port 8442; however, when attempting to access it via port 8443, the browser (Chrome on Windows 10) prompts me to select a certificate. When I select the correct certificate, the authentication appears to fail, and the system switches to an alternative authentication method, asking me to enter a username and password instead. An important detail: if I provide an incorrect certificate, the connection is denied—as expected—so the problem specifically lies with the correct certificate. I suspect this issue may be related to the WildFly version, as I followed the exact same steps I previously used with version 24.0.1, and it worked correctly back then. Here are other troubleshooting steps I have tried, all of which resulted in the same behavior:

1- I generated a new superAdmin.p12 file.
2- I reviewed the logs and did not find anything unusual.
3- I updated my web browser.

[primetomas]

Is that URL the link you go to directly? Try to end with just "adminweb".

[primetomas]

It could be something with how you configured the new wildfly. I'd anyhow recommend upgrading to the latest version. Upgrade from EJBCA 7 to 9 should be easy.

[erlispaula-coder]

Hello—in the end, I wasn't able to perform the restore using WildFly 25.0.0. I tried using version 26.0.1 instead and was able to successfully complete the task. It seems that for EJBCA 7.11.0 on WildFly 25.0.0, something changes or requires additional configuration. Best regards to everyone, and thank you @primetomas