Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compatibility with OpenXPKI #225

Open
tobuh opened this issue Dec 21, 2023 · 1 comment
Open

Compatibility with OpenXPKI #225

tobuh opened this issue Dec 21, 2023 · 1 comment

Comments

@tobuh
Copy link

tobuh commented Dec 21, 2023

Hi

Anyone tried to use this client with OpenXPKI server?

I tried to run the client, but got errors:
ts=2023-12-21T15:56:06.228258504Z level=info op=PKIOperation error="http request failed with status 400 Unable to parse request, msg: [some binary data]

I use initial docker config for OpenXPKI. The setup is succesfully tested with sscep.

Greetings
Tobi

@tobuh
Copy link
Author

tobuh commented Jan 2, 2024

Meanwhile, I made a little progress. I enabled tracing on OpenXPKI and noticed some differences to SSCEP.

SSCEP uses content type "application/pkcs7", so I changed this manually in func EncodeSCEPRequest.

The other topic is the transaction id. I noticed a regex error on OpenXPKI side. SSCEP provides a hexadecimal string (e.g. "71BE711D014F473E51499455F3D32431"), while this library uses base64 encoding. I temporarily hardcoded the transaction id.

With both things changed I could successfully receive a certificate. How to proceed now? Who is out of specification? How do other servers behave? Can I overwrite the behaviour while calling the library? If yes, how?

Renewal is still not working (400 Signature invalid), but this still needs some proper investigation on my side.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant