From: Shan Shaji <s.shaji@proxmox.com>
To: pdm-devel@lists.proxmox.com
Cc: Shan Shaji <s.shaji@proxmox.com>
Subject: [pdm-devel] [PATCH datacenter-manager] fix #6794: api: allow non-root users to view stats on dashboard
Date: Fri, 19 Sep 2025 17:11:05 +0200 [thread overview]
Message-ID: <20250919151105.348900-1-s.shaji@proxmox.com> (raw)
When a non-root user logged into PDM, the Top Entities section was
not visible, even though the required privileges had been assigned.
To fix it allow all authenticated users to access the `/top-entities`
endpoint. Also added explicit privilege checks to validate the access
on resources.
Signed-off-by: Shan Shaji <s.shaji@proxmox.com>
---
server/src/api/resources.rs | 23 ++++++++++++++++++--
server/src/metric_collection/top_entities.rs | 5 +++++
2 files changed, 26 insertions(+), 2 deletions(-)
diff --git a/server/src/api/resources.rs b/server/src/api/resources.rs
index ce05db1..4012353 100644
--- a/server/src/api/resources.rs
+++ b/server/src/api/resources.rs
@@ -475,6 +475,9 @@ pub async fn get_subscription_status(
// FIXME: make timeframe and count parameters?
// FIXME: permissions?
#[api(
+ access: {
+ permission: &Permission::Anybody,
+ },
input: {
properties: {
"timeframe": {
@@ -485,11 +488,27 @@ pub async fn get_subscription_status(
},
)]
/// Returns the top X entities regarding the chosen type
-async fn get_top_entities(timeframe: Option<RrdTimeframe>) -> Result<TopEntities, Error> {
+async fn get_top_entities(
+ timeframe: Option<RrdTimeframe>,
+ rpcenv: &mut dyn RpcEnvironment,
+) -> Result<TopEntities, Error> {
+ let user_info = CachedUserInfo::new()?;
+ let auth_id: Authid = rpcenv
+ .get_auth_id()
+ .ok_or_else(|| format_err!("no authid available"))?
+ .parse()?;
+
+ if !user_info.any_privs_below(&auth_id, &["resource"], PRIV_RESOURCE_AUDIT)? {
+ http_bail!(UNAUTHORIZED, "user has no access to resources");
+ }
+
let (remotes_config, _) = pdm_config::remotes::config()?;
+ let check_remote_privs = |remote_name: &str| {
+ user_info.lookup_privs(&auth_id, &["resource", remote_name]) & PRIV_RESOURCE_AUDIT != 0
+ };
let timeframe = timeframe.unwrap_or(RrdTimeframe::Day);
- let res = top_entities::calculate_top(&remotes_config, timeframe, 10);
+ let res = top_entities::calculate_top(&remotes_config, timeframe, 10, check_remote_privs);
Ok(res)
}
diff --git a/server/src/metric_collection/top_entities.rs b/server/src/metric_collection/top_entities.rs
index 47fda24..990189a 100644
--- a/server/src/metric_collection/top_entities.rs
+++ b/server/src/metric_collection/top_entities.rs
@@ -36,12 +36,17 @@ pub fn calculate_top(
remotes: &HashMap<String, pdm_api_types::remotes::Remote>,
timeframe: proxmox_rrd_api_types::RrdTimeframe,
num: usize,
+ check_remote_privs: impl Fn(&str) -> bool
) -> TopEntities {
let mut guest_cpu = Vec::new();
let mut node_cpu = Vec::new();
let mut node_memory = Vec::new();
for remote_name in remotes.keys() {
+ if !check_remote_privs(remote_name) {
+ continue;
+ }
+
if let Some(data) =
crate::api::resources::get_cached_resources(remote_name, i64::MAX as u64)
{
--
2.47.2
_______________________________________________
pdm-devel mailing list
pdm-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pdm-devel
reply other threads:[~2025-09-19 15:11 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=20250919151105.348900-1-s.shaji@proxmox.com \
--to=s.shaji@proxmox.com \
--cc=pdm-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.