I'm trying to configure Proxmox VE with Pocket ID OIDC.
Here are two guides:
Both guides state that to correctly create a user, you must specify "Select username for the Username Claim dropdown. (This is a personal preference and controls how the username is shown, for example: username = username@PocketID or email = username@example@PocketID)."
However, in version 9.2.10, I can't specify a Username Claim—I have the Default parameter set to a text value (there's no select list or text input field).
As a result, everything works, but users have usernames in the unfriendly format 20140736-b949-45f1-a22b-d6aa0c974647@PocketID.
Is this a fundamental developer decision or a bug? When trying to add this parameter from the shell, I get the error:
This parameter is documented in the official documentation: https://pve.proxmox.com/pve-docs/pveum.1.html
Therefore, I didn't risk editing the /etc/pve/domains.cfg file manually. Can anyone explain what I'm doing wrong?
Here are two guides:
- https://pocket-id.org/docs/client-examples/proxmox
- https://rabin.blog/how-to-configure-pocket-id-passkey-login-for-proxmox-ve-with-oidc-groups/
Both guides state that to correctly create a user, you must specify "Select username for the Username Claim dropdown. (This is a personal preference and controls how the username is shown, for example: username = username@PocketID or email = username@example@PocketID)."
However, in version 9.2.10, I can't specify a Username Claim—I have the Default parameter set to a text value (there's no select list or text input field).
As a result, everything works, but users have usernames in the unfriendly format 20140736-b949-45f1-a22b-d6aa0c974647@PocketID.
Is this a fundamental developer decision or a bug? When trying to add this parameter from the shell, I get the error:
Bash:
pveum realm modify PocketID --username-claim email
Unknown option: username-claim
400 unable to parse option
pveum realm modify <realm> [OPTIONS]This parameter is documented in the official documentation: https://pve.proxmox.com/pve-docs/pveum.1.html
Therefore, I didn't risk editing the /etc/pve/domains.cfg file manually. Can anyone explain what I'm doing wrong?
