From: Kai Hamilton via pve-devel <pve-devel@lists.proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: Kai Hamilton <kai.hamil@gmail.com>
Subject: [pve-devel] Tested-by: kai.hamil@gmail.com (Requesting permission / capability to test)
Date: Sat, 19 Jul 2025 05:24:40 -0700 [thread overview]
Message-ID: <mailman.98.1753366969.367.pve-devel@lists.proxmox.com> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 5819 bytes --]
From: Kai Hamilton <kai.hamil@gmail.com>
To: pve-devel@lists.proxmox.com
Subject: Tested-by: kai.hamil@gmail.com (Requesting permission / capability to test)
Date: Sat, 19 Jul 2025 05:24:40 -0700
Message-ID: <CAGHu1Kd6gSf-HaO25X4m_sbGsBy0nvj9-Bb1iA=pVaQAnnmffw@mail.gmail.com>
Hello proxmox developers,
I am very interested in the steps to build the patch for OIDC integrations
such as zitadel which need a custom audiences field as seen in the issues I
contained at the footer of this message. I would love to build this in my
production proxmox instance if given hints to where I might learn about
these steps I would be able to provide feedback on future patches before
they are committed to the active release of proxmox community editions as
I do not have an enterprise license.
Thank you for your correspondence on this matter, and apologies if I would
not be the target user to pursue this capability. Huge thanks to the
proxmox development team! I love proxmox enough that I would hope to build
a business around it. The dream is to require an enterprise license one day!
Warm regards,
Kai a.k.a. "SoFMeRight"
precisionplanit.com / sofmeright.com
https://lore.proxmox.com/all/999303783.1030.1748874882155@webmail.proxmox.com/
https://bugzilla.proxmox.com/show_bug.cgi?id=5076
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
reply other threads:[~2025-07-24 14:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=mailman.98.1753366969.367.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=kai.hamil@gmail.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