Details
-
Improvement
-
Resolution: Won't Do
-
Major
-
None
-
None
Description
A couple of the configuration property names (esp. attributes mappings) are confusing: some are unused; others are used to map their value to the Magnolia User class: in this case they should probably have a name that's meaningful to Magnolia, instead of the not-so-standard ldap naming schemes: GivenName could be "fullname" for instance.
Ideally we should change this but still allow the old ones to be used..
Checklists
Acceptance criteria