API "Error no client certificate or OAuth token received for authentication." response when enrolling #872
Unanswered
mharrisistl
asked this question in
Q&A
Replies: 1 comment
-
If you stared the container with "TLS_SETUP=simple" client cert authentication to the RA web does not work. You need to make a "proper" certificate configuration installation. Does your giveoutcerts.p12 client certificate link up to a CA that is added to the TLS trust store? Otherwise it can not be used for client authentication. Try first with the same certificate you use to access to admin UI, if that works you know it's just your client certificate configuration. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all
Slowly learning EJBCA ( and security in general ) but have become stuck when trying to enrol through the rest api. I have been following the Keyfactor tutorials on youtube, specifically these :
https://youtu.be/dYrrrQLo16Q?si=ub9WldOdvkGGcbG4
https://youtu.be/Eh3To9SNP50?si=UmxPK0eCu1NuJ-h6
I unfortunately get this error when trying to use Postman and unsure why:
{ "error_code": 403, "error_message": "Error no client certificate or OAuth token received for authentication." }
Current set up in Postman:
CA Certificate -> IssuingCA.pem
Client Certificate -> giveoutcerts.p12
EJBCA setup ( I think I have covered everything ):
Certificate profiles:
Root CA profile ( Root CA )
Issuing CA profile ( Sub CA )
End Entity Profile ( End Entity )
Certificate authorities:
My Root CA
issuing CA
End Entity Profile:
End Entity
Can see CA certificates and the End Entity in EJBCA RA GUI.
Modified roles and members so that it has needed permissions.
Checked that crypto tokens and CA's are activate.
Is there anything I have missed or set up wrong?
Beta Was this translation helpful? Give feedback.
All reactions