Oven should support the acme.json standard #1800
Unanswered
chaos-dotcom
asked this question in
Ideas
Replies: 2 comments
-
|
Oh, this is an area we haven't touched on yet. Thank you. If you could PR it, everyone in this community would benefit. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
In real environments, services such as reverse proxies often include support for ACME. |
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.
-
As per RFC8555 - https://www.rfc-editor.org/rfc/rfc8555.html
The ACME protocol uses JSON-formatted messages to manage certificates, including issuance, renewal, and revocation. The Automated Certificate Management Environment (ACME) is defined in RFC 8555.
This format is becoming more common place within the HTTPS universe, and uses JSON formatting for each part of a certificate so should be relatively easy to parse from and read the values that oven requries.
It also has advantage of only being one file that you have to link to and not 3 separate files, so it should make for a more fluid deploying process
Beta Was this translation helpful? Give feedback.
All reactions