Allow any attributes in mapping and include in results
When using attribute mapping (e.g., user_additional_attribute_mapping), any
attributes that Keystone didn't know about were ignored and a warning was
issued, like
WARNING keystone.common.ldap.core [-] Invalid additional attribute mapping:
"description:description". Value "description" must use one of password,
enabled, default_project_id, name, email.
This check is removed. Additional attribute mappings for "unexpected"
attributes (such as description) should be allowed. For one thing, all the
known attributes already have a way of setting the mapping, via the
user_*_attribute config option. This will allow setting a "description" or
any other attribute mapping for users.
The extra attributes defined in the *_additional_attribute_mapping config
options weren't included in the list results. These attributes should be
included in the list results.
This is a combination of 3 commits from master:
(cherry picked from commit 17db03164200f0d7fff564058fc7df8e97705523)
(cherry picked from commit 10051adace7cd728d46cd4c999e3019fdbf2d961)
(cherry picked from commit ebfdab034f2b35074f1645b70c1f07d0c4dfd337)
Reviewed: https:/ /review. openstack. org/91490 /git.openstack. org/cgit/ openstack/ keystone/ commit/ ?id=b9323212128 97ca18ea4fd566d 73c9d86b781182
Committed: https:/
Submitter: Jenkins
Branch: stable/icehouse
commit b932321212897ca 18ea4fd566d73c9 d86b781182
Author: Brant Knudson <email address hidden>
Date: Mon Mar 17 13:41:32 2014 -0500
Allow any attributes in mapping and include in results
When using attribute mapping (e.g., user_additional _attribute_ mapping) , any
attributes that Keystone didn't know about were ignored and a warning was
issued, like
WARNING keystone. common. ldap.core [-] Invalid additional attribute mapping: on:description" . Value "description" must use one of password,
"descripti
enabled, default_project_id, name, email.
This check is removed. Additional attribute mappings for "unexpected" *_attribute config option. This will allow setting a "description" or
attributes (such as description) should be allowed. For one thing, all the
known attributes already have a way of setting the mapping, via the
user_
any other attribute mapping for users.
The extra attributes defined in the *_additional_ attribute_ mapping config
options weren't included in the list results. These attributes should be
included in the list results.
This is a combination of 3 commits from master: 7fff564058fc7df 8e97705523) 8d46cd4c999e301 9fdbf2d961) 74f1645b70c1f07 d0c4dfd337)
(cherry picked from commit 17db03164200f0d
(cherry picked from commit 10051adace7cd72
(cherry picked from commit ebfdab034f2b350
Change-Id: Ia80174063a5eac def690ca378b7cb 71300a5f5f8
Closes-Bug: #1293698