Feature request: Support for controlling PVE Authentication Server password hashesSee original GitHub issue
Setting the initial password via Ansible might not be desireable in all situations.
In some situations, it might be preferable to provide the contents of the SHA-256 crypt directly.
This should probably work so that current
password parameter is completely ignored if the hash is provided. Unsure if this would mean big or small changes for
create_user(). For any of this to work,
/etc/pve/priv/shadow.cfg would probably need to be taken under control of this role.
- Created a year ago
- Comments:13 (12 by maintainers)
Top GitHub Comments
The main reason for this ticket is to have a PVE integrated user management. I wondered myself, why I don‘t had the problem before and maybe I just want to give a hint: I‘m using the PAM users. This users are managed via Ansible too, they cannot login via SSH but have a physical user account on the host. Together with the Proxmox groups and roles a useful ACL management is already present via pvesh. I don‘t know if the PVE integrated access management is something, that will be developed in the future. I would expect, that they wanna switch more to LDAP, OAuth or something like that, which is more an enterprise feature. And use PAM for community solutions. But - you should ask them as proposed. From my perspective - use PAM. Am 24.10.2022 um 13:14 schrieb Musee Ullah @.***>: I think you should be able to open a feature request on their issue tracker (my memory is hazy but I think it was public somewhere?) or post on the pve-user mailing list. Developers have been pretty responsive in my experience.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>