rest-api enable fail

[steven-designlibro]

I turned on the interface of the v1 version, but it doesn't seem to have any effect.

[primetomas]

What version of EJBCA?

[steven-designlibro]

I'm using docker image “keyfactor/ejbca-ce:8.3.1”

This is my startup command.

docker run -it -d --name=ejbca-8.3.1  -p 80:8080 -p 443:8443 -p 8080:8080 -p 8443:8443  -h localhost -e TLS_SETUP_ENABLED="true" keyfactor/ejbca-ce:8.3.1

[primetomas]

EJBCA 9.0 is out. You can upgrade to this.

Try to check, save, uncheck, save the custom header checkbox. That did it for me. If that works for you it may be a display issue in the UI.

[primetomas]

Yes you need client certificate authentication.
Here is a couple of good resources for remotely calling the REST API.
https://github.com/Keyfactor/ejbca-easy-rest-client
https://github.com/Keyfactor/ejbca-go-client-sdk

Or just use cURL:
https://docs.keyfactor.com/ejbca/latest/ejbca-rest-interface#id-(9.1.1)EJBCARESTInterface-IntegratingwiththeRESTAPI

[steven-designlibro]

You are right. i can check how it is implemented in two other ways, but the fundamental reason is how to obtain the two certificates java-sdk. If it is based on easy-rest-client, there will be a lot of development tasks. Does it feel that java-sdk has stopped updating?

[primetomas]

I just haven't used the java client myself. I guess you mean this one?
https://github.com/Keyfactor/ejbca-java-client-sdk

You have to see what error you get there and configure accordingly. getting the client key and cert from superadmin.p12 should work fine.
I notice that the example doesn't set setSslCaCert which may be needed for the TLS connection, unless you set setVerifyingSsl(false).

I just haven't tested that myself.

[steven-designlibro]

Well, I can only explore slowly. setVerifyingSsl(false) has been set in the demo. Except for the interface return exceptions, there is no abnormality in sdk work，thank you very much