You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The upsd.users template checks each user option type and if it's a non-string iterable, it creates a multi-line repeat of the option. If a user password is encrypted with ansible vault, it is iterable, but not type string, therefore causing the password to be split out into many "password=" lines with each containing a single character. This is because the type of the password string is AnsibleVaultEncryptedUnicode, not string.
My proposed fix is to test if option name is password and always treat that as a single string since upsd.users does not support multiple passwords for a user anyway. Anything given to the template as a password key should be a single string.
If that solution is amenable, I can have a PR ready in a few minutes.
The text was updated successfully, but these errors were encountered:
This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!
github-actionsbot
added
the
stale
This issue or pull request has been marked 'stale' due to lack of recent activity
label
Nov 13, 2024
vladgh
removed
the
stale
This issue or pull request has been marked 'stale' due to lack of recent activity
label
Nov 13, 2024
The
upsd.users
template checks each user option type and if it's a non-string iterable, it creates a multi-line repeat of the option. If a user password is encrypted with ansible vault, it is iterable, but not type string, therefore causing the password to be split out into many "password=" lines with each containing a single character. This is because the type of the password string is AnsibleVaultEncryptedUnicode, not string.My proposed fix is to test if option name is password and always treat that as a single string since upsd.users does not support multiple passwords for a user anyway. Anything given to the template as a password key should be a single string.
If that solution is amenable, I can have a PR ready in a few minutes.
The text was updated successfully, but these errors were encountered: