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

Support different CA #32

Open
espen opened this issue Mar 4, 2022 · 2 comments
Open

Support different CA #32

espen opened this issue Mar 4, 2022 · 2 comments

Comments

@espen
Copy link
Contributor

espen commented Mar 4, 2022

Have you considered supporting different CAs? I don't know so much about ACME works but it seems to be it should be just switching the URL? Then again I don't know ACME so I could be wrong here. So https://zerossl.com could be supported? I guess it would require some naming changes in this gem though :)

btw this gem looks great. I was hoping not to use it though as I would prefer to outsource cert handling (using ZeroSSL REST API - but they do not give out the private key in the API), so if I have to implement it this gem looks like a very good option.

@elct9620
Copy link
Owner

elct9620 commented Mar 4, 2022

If the Let's Encrypt API is implemented, I think it can support other providers. I had read the ZeroSSL a few years ago, I think I didn't try to support it because I have a similar problem you are mentioned.

@espen
Copy link
Contributor Author

espen commented Mar 7, 2022

It is my understanding that both Let's Encrypt and ZeroSSL have the same ACME API. There seems to be some authentication differences that will be supported in acme-client soon: unixcharles/acme-client#210

When that is supported it should be sufficient for this gem to offer a way to change the endpoint as well as supplying the additional required credentials needed for zerossl.

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

2 participants