Comment 3 for bug 1542417

Rudolf Vriend (rudolf-vriend) wrote :

No. Unfortunatily that doesn't work.

The user_additional_attribute_mapping (self.extra_attr_mapping) is ignored in the attribute mapping code after a LDAP get operation. Except for the 'special' case where 'description' is mapped to 'description' due to the attribute_mapping..get(k, k) (see https://github.com/openstack/keystone/blob/master/keystone/common/ldap/core.py#L1359).

Since the user_additional_attribute_mapping seems to be only evaluated during LDAP create (https://github.com/openstack/keystone/blob/master/keystone/common/ldap/core.py#L1433) which has been deprecated, I think it does make sense that either a user_description_attribute config is supported or the user_additional_attribute_mapping is evaluated after LDAP get operations.

For our use-cases a user.description is definitely a need to have, since user name & email aren't necessarily very expressive.

see also: https://bugs.launchpad.net/keystone/+bug/1336769