From: Christoph Heiss <c.heiss@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs] pveum: document correct path for ldap/realm credentials
Date: Fri, 28 Mar 2025 13:07:25 +0100 [thread overview]
Message-ID: <20250328120803.1096838-1-c.heiss@proxmox.com> (raw)
/etc/pve/priv/realm has been the default path since commit
782b702db ("auth ldap/ad: make password a parameter for the api")
That commit was part of pve-access-control 6.0-7.
Replace /etc/pve/priv/ldap with /etc/pve/priv/realm, to avoid pointing
users to the deprecated path.
It's not used anywhere in our code too, except as (very) old fallback.
Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
---
pveum.adoc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/pveum.adoc b/pveum.adoc
index 0cc267e..c5fbd46 100644
--- a/pveum.adoc
+++ b/pveum.adoc
@@ -224,8 +224,8 @@ attribute would be `uid`.
If {pve} needs to authenticate (bind) to the LDAP server before being
able to query and authenticate users, a bind domain name can be
configured via the `bind_dn` property in `/etc/pve/domains.cfg`. Its
-password then has to be stored in `/etc/pve/priv/ldap/<realmname>.pw`
-(for example, `/etc/pve/priv/ldap/my-ldap.pw`). This file should contain a
+password then has to be stored in `/etc/pve/priv/realm/<realmname>.pw`
+(for example, `/etc/pve/priv/realm/my-ldap.pw`). This file should contain a
single line with the raw password.
To verify certificates, you need to set `capath`. You can set it either
--
2.48.1
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-03-28 12:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 12:07 Christoph Heiss [this message]
2025-04-04 10:19 ` [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=20250328120803.1096838-1-c.heiss@proxmox.com \
--to=c.heiss@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal