From 843691f8b4581acac08fae8d17aa5b6a675eaae3 Mon Sep 17 00:00:00 2001 From: gyptazy Date: Mon, 7 Apr 2025 15:51:44 +0200 Subject: [PATCH] docs: Adjust docs regarding API Token and priviledge separation. Fixes: #164 --- docs/03_configuration.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/03_configuration.md b/docs/03_configuration.md index a77b711..f011c1d 100644 --- a/docs/03_configuration.md +++ b/docs/03_configuration.md @@ -44,7 +44,10 @@ pveum acl modify / --roles proxlb --users proxlb@pve pveum user token add proxlb@pve proxlb ``` -Afterwards, you get the token secret returned. You can now add those entries to your ProxLB config. Make sure, that you also keep the `user` parameter, next to the new token parameters. The parameter `pass` then needs to be **absent**. +Afterwards, you get the token secret returned. You can now add those entries to your ProxLB config. Make sure, that you also keep the `user` parameter, next to the new token parameters. + +> [!IMPORTANT] +> The parameter `pass` then needs to be **absent**! You should also take care about the privilege and authentication mechanism behind Proxmox. You might want or even might not want to use privilege separation and this is up to your personal needs and use case. | Proxmox API | ProxLB Config | Example | |---|---|---|