Document that attributes must be defined in an attributes hash
What does this MR do and why?
While helping a customer (internal link) I discovered that we don't actually mention that attributes
must have its own subsection in the LDAP config. This docs MR addresses that.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.