From: Folke Gleumes <f.gleumes@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH manager 0/2] fix #5093 add custom directory and eab to ui
Date: Tue, 16 Jan 2024 15:49:12 +0100 [thread overview]
Message-ID: <78d597f8c83716882768eb95d482fa3c8b7cd72c.camel@proxmox.com> (raw)
In-Reply-To: <20240116143338.294260-1-f.gleumes@proxmox.com>
For testing, I have used pebble [0] in a separate lxc container.
1. Download and compile the project
2. Start pebble with the included eab config:
pebble -c test/config/pebble-config-external-account-bindings.json
3. Import the certificates from the test/certs folder into the pve
instance
4. Add the pebble to the /etc/hosts of your pve instance
5. Use https://pebble:14000/dir as the acme directory for testing, eab
credentials can be found in the config used in step 2
[0] https://github.com/letsencrypt/pebble
On Tue, 2024-01-16 at 15:33 +0100, Folke Gleumes wrote:
> This patch series adds the option to set a custom directory for ACME
> and
> enables the user to use external account binding, which is required
> by
> some providers.
>
> Folke Gleumes (2):
> fix #5093: webui: acme: custom directory option
> webui: acme: add eab fields
>
> www/manager6/node/ACME.js | 168 ++++++++++++++++++++++++++++++------
> --
> 1 file changed, 135 insertions(+), 33 deletions(-)
>
next prev parent reply other threads:[~2024-01-16 14:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 14:33 Folke Gleumes
2024-01-16 14:33 ` [pve-devel] [PATCH manager 1/2] fix #5093: webui: acme: custom directory option Folke Gleumes
2024-04-17 14:34 ` Mira Limbeck
2024-01-16 14:33 ` [pve-devel] [PATCH manager 2/2] webui: acme: add eab fields Folke Gleumes
2024-01-16 14:49 ` Folke Gleumes [this message]
2024-04-16 8:46 ` [pve-devel] [PATCH manager 0/2] fix #5093 add custom directory and eab to ui Folke Gleumes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=78d597f8c83716882768eb95d482fa3c8b7cd72c.camel@proxmox.com \
--to=f.gleumes@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox