* Include custom attributes when bootstrapping user and group configs
* Fix logic to detect user/group config without custom attributes
* Increase readability of query definition using a heredoc
* Remove duplicate query variables and improve readability
* Revert "Increase readability of query definition using a heredoc"
This reverts commit 7a73dacc21.
* example_config: moving nslcd old guide to NSLCD.md
* example_config: creating README for SSSD
* example_config: creating sssd.conf
* example_config: removing explicit links and adding a reference to the old NSLCD guide
* example_config: fixing images in pam README
* example_config: add how to enable automatic home directory creation
* example_config: fixing typo in command to edit ssh config
* example_config: using commments instead of line numbers for the example sssd.conf file
---------
Co-authored-by: nitnelave <valentin@tolmer.fr>
Found that only a restart of Home Assistant will read the new lines in configuration.yaml. Also added a note to use `-k` when using the curl command if needed.
The fields first_name, last_name, and avatar have all been moved
to regular attributes in the database, and are available through
the GraphQL API as such as well. This commit removes the legacy
fields for each on the internal CreateUserRequest type, leaving
these to only be updateable through attributes.
The fields are still available in the GraphQL CreateUserInput
type, preserving backwards compatiblity, and if set, they will
be used for the corresponding attribute values. If both fields
and attributes are set, the values given through attributes will
superceed the fields, and be used. This change also fixes a bug,
where creation of a user would fail if either of these attributes
were set as both attribute and field, as it would attempt to
insert the attribute twice, violating a unique constraint in the
database.
Antonio Vargas