From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: pmg-devel@lists.proxmox.com
Subject: [pmg-devel] [PATCH pmg-api 4/4] api: users: rework userid validation
Date: Wed, 26 Feb 2025 20:17:02 +0100 [thread overview]
Message-ID: <20250226191702.584119-5-s.ivanov@proxmox.com> (raw)
In-Reply-To: <20250226191702.584119-1-s.ivanov@proxmox.com>
reuse the existing helpers in PMG::Utils to forbid creating:
* users with an unallowed realm
* passing a different realm than what we receive in the userid
* users in the pam realm
Reported-by: Mira Limbeck <m.limbeck@proxmox.com>
Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
---
src/PMG/API2/Users.pm | 16 ++++++++++++----
1 file changed, 12 insertions(+), 4 deletions(-)
diff --git a/src/PMG/API2/Users.pm b/src/PMG/API2/Users.pm
index f137b87..1edf29a 100644
--- a/src/PMG/API2/Users.pm
+++ b/src/PMG/API2/Users.pm
@@ -111,9 +111,6 @@ __PACKAGE__->register_method ({
die "User '$param->{userid}' already exists\n"
if $cfg->{$param->{userid}};
- die "Currently you cannot create user in the PAM realm\n"
- if $param->{realm} && $param->{realm} eq 'pam';
-
my $entry = {};
foreach my $k (keys %$param) {
my $v = $param->{$k};
@@ -124,10 +121,21 @@ __PACKAGE__->register_method ({
}
}
+ my ($userid, $username, $realm) = PMG::Utils::verify_username($entry->{userid});
+ my $realm_regex = PMG::Utils::valid_pmg_realm_regex();
+ die "invalid realm in userid\n" if $realm !~ /$realm_regex/;
+
+ if ($entry->{realm}) {
+ die "realm parameter does not fit userid\n" if ($entry->{realm} ne $realm);
+ } else {
+ $entry->{realm} = $realm;
+ }
+
+ die "Currently you cannot create user in the PAM realm\n" if $entry->{realm} eq 'pam';
+
$entry->{enable} //= 0;
$entry->{expire} //= 0;
$entry->{role} //= 'audit';
- $entry->{realm} //= 'pmg';
$cfg->{$param->{userid}} = $entry;
--
2.39.5
_______________________________________________
pmg-devel mailing list
pmg-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pmg-devel
next prev parent reply other threads:[~2025-02-26 19:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 19:16 [pmg-devel] [PATCH pmg-api 0/4] cleanups for OIDC patch-series Stoiko Ivanov
2025-02-26 19:16 ` [pmg-devel] [PATCH pmg-api 1/4] api: authrealm: create: add quarantine as reserved realm Stoiko Ivanov
2025-02-26 20:18 ` [pmg-devel] applied: " Thomas Lamprecht
2025-02-26 19:17 ` [pmg-devel] [PATCH pmg-api 2/4] utils: drop unused variable assignment Stoiko Ivanov
2025-02-26 20:18 ` Thomas Lamprecht
2025-02-26 19:17 ` [pmg-devel] [PATCH pmg-api 3/4] utils: user schema: explicitly forbid @ in user-names Stoiko Ivanov
2025-02-26 20:18 ` Thomas Lamprecht
2025-02-26 19:17 ` Stoiko Ivanov [this message]
2025-02-26 20:19 ` [pmg-devel] applied: [PATCH pmg-api 4/4] api: users: rework userid validation Thomas Lamprecht
2025-02-26 19:32 ` [pmg-devel] [PATCH pmg-api 0/4] cleanups for OIDC patch-series Stoiko Ivanov
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=20250226191702.584119-5-s.ivanov@proxmox.com \
--to=s.ivanov@proxmox.com \
--cc=pmg-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