REST API connectivity issue

[ryanjtuck]

Hello All,

I'm fairly new to PKI specifics but have had a lot of interactions with CAs as a client while working as a network engineer. I provide this background as my question is multifaceted.

I'm trying to request a certificate from my EJBCA instance via Postman. I have enabled REST in the configuration, and there is end-to-end connectivity. Based on my research, I have been using the following URL:

https://XX.XX.XX.XX:8443/ejbca/ejbca-rest-api/v1/certificates/pkcs10enroll

However, I found that the server is not listening on port 8443. When I change the URL to use port 443, I get no response, and nothing appears in the RA logs or the Admin portal—despite the port being open.

My questions:

What is the correct URL for making a client certificate request via REST API in EJBCA?

Am I using the correct process for requesting a client certificate where the keys are generated on the server i.e pkcs10enroll?

I'm happy to provide any logs, configuration files, or further explanations if needed. Any guidance would be greatly appreciated!

Thanks in advance!

[primetomas]

Depending on how you install EJBCA your port can be different, i.e. it's a WildFly configuration.
Assuming you can access the Admin UI, the REST API works on the same port as the Admin UI, and if you can access the UI it clearly listens on that port.
Something to have in mind is that that REST API end point require TLS client certificate authentication, so if you don't use that the connection will terminate immediately in the TLS layer without anything coming into EJBCA.

[ryanjtuck]

The Admin UI is present without the use of explicit port, the assumption being its 442. as the REST post to the cert url on port 442 results in a socket hang up. to test if all services are up on this port.

I have tried to navigate to https://172.164.248.52:442/ejbca/doc/rest/) with and without the port and it just times out.

I have added the correct certs to postman so it should be able to establish TLS.

[primetomas]

I can’t really guess how you have configured your ports unless you give more information about your configuration.
what I can say is that https without a specific port specified in a web browser uses port 443.