ansible/changelogs/fragments/postgresql_user-encrypted-fixes.yml

---
minor_changes:
- "`postgresql_user` module changed `encrypted=yes` to be the default. This
   shouldn't break any current playbooks, the module will just store passwords
   hashed by default. This change was done because Postgres 10 dropped support for
   `UNENCRYPTED` passwords and because all versions since Postgres 7.2 support
   storing encrypted passwords."
postgresql_user: set encrypted as default and fix empty password reporting changed (#36931) * Set encrypted as default and fix empty password reporting changed * Starting with Postgres 10 `UNENCRYPTED` passwords are removed and because of that this module fails with the default `encrypted=no`. Also encrypted passwords are suported since version 7.2 (https://www.postgresql.org/docs/7.2/static/sql-createuser.html) which went EOL in 2007 and since 7.3 it is the default. Because of this it makes a lot more sense to make `encrypted=yes` the default. This won't break backward compatibility, the module would just update the user's password in the DB in the hashed format and everything else will work like before. It's also a security bad practice to store passwords in plain text. fixes #25823 * There was also a bug with `encrypted=yes` and an empty password always reported as changed. * Improved documentation for `encrypted`/`password` parameters, and removed some obsolete notes about passlib. * Fix clearing user's password to work with all versions of Postgres * Add tests for clearing the user password * Fix documentation atfer rebase * Add changelog fragment 2018-05-21 21:49:44 +02:00			`---`
			`minor_changes:`
			- "`postgresql_user` module changed `encrypted=yes` to be the default. This
			`shouldn't break any current playbooks, the module will just store passwords`
			`hashed by default. This change was done because Postgres 10 dropped support for`
			`UNENCRYPTED` passwords and because all versions since Postgres 7.2 support
			`storing encrypted passwords."`