From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Dominik Csapak <d.csapak@proxmox.com>
Subject: Re: [pve-devel] [PATCH widget-toolkit] window: acme account: hide e-mail field if it does not exist
Date: Fri, 3 Oct 2025 14:23:34 +0200 [thread overview]
Message-ID: <5fd60be7-7597-40ae-9f7d-9c820ce5276a@proxmox.com> (raw)
In-Reply-To: <20251002112528.3128880-1-d.csapak@proxmox.com>
Am 02.10.25 um 13:25 schrieb Dominik Csapak:
> it seems that currently, the account information returned by letsencrypt
> does not include the contact anymore, so there is no 'contact' field in
> the 'account' property.
>
> To not trip up the ui, only optionally read that out, and hide the field
> completely if it does not exist.
>
> Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
> ---
> I looked in the backend, we save the 'account' object verbatim from the
> api response, and the RFC [0] says it should have a contact field, but
> it's not there in my tests with the staging + normal api, so not sure
> if this is the right fix.
>
This is probably the result from Let's Encrypt stopping to send expiry
notification emails a few months ago, see:
https://letsencrypt.org/2025/01/22/ending-expiration-emails
As that article also talk about not wanting to handle email addresses
in general, they might just have dropped the support for real.
> 0: https://www.rfc-editor.org/rfc/rfc8555#section-9.7.1
>
> src/window/ACMEAccount.js | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/src/window/ACMEAccount.js b/src/window/ACMEAccount.js
> index 095e674..939ddf2 100644
> --- a/src/window/ACMEAccount.js
> +++ b/src/window/ACMEAccount.js
> @@ -191,10 +191,11 @@ Ext.define('Proxmox.window.ACMEAccountView', {
> me.load({
> success: function (response) {
> var data = response.result.data;
> - data.email = data.account.contact[0];
> + data.email = data.account.contact?.[0];
> data.createdAt = data.account.createdAt;
> data.status = data.account.status;
> me.setValues(data);
> + me.down('field[name=email]').setHidden(!data.email);
> },
> });
> },
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-10-03 12:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 11:17 Dominik Csapak
2025-10-03 12:23 ` Thomas Lamprecht [this message]
2025-10-03 12:27 ` [pve-devel] applied: " Thomas Lamprecht
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=5fd60be7-7597-40ae-9f7d-9c820ce5276a@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=d.csapak@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