yahoo-eng-team team mailing list archive

[OpenStack Infra <1542417@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/276873
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=448778a51126a79676e9f9ffcc9eaf4c06288a73
Submitter: Jenkins
Branch:    master

commit 448778a51126a79676e9f9ffcc9eaf4c06288a73
Author: Rudolf Vriend <rudolf.vriend@xxxxxxx>
Date:   Fri Feb 5 19:58:53 2016 +0100

    Adds user_description_attribute mapping support to the LDAP backend
    
    The LDAP backend supports mapping between LDAP and keystone user
    attributes via the 'user_<attribute_name>_attribute' settings in the
    LDAP driver configuration.
    
    The current implementation is incomplete, since there is no support for
    specifying a 'user_description_attribute' setting for user get (read)
    operations.
    
    This change adds support to the LDAP backend for mapping of user
    description attributes via a 'user_description_attribute' configuration
    also during user retrieval.
    
    Change-Id: I30b63306beae3379aa8c29d0df3f327369d3f2a6
    Closes-Bug: #1542417


** Changed in: keystone
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1542417

Title:
  LDAP backend lacks support for user_description_attribute mapping

Status in OpenStack Identity (keystone):
  Fix Released

Bug description:
  The LDAP backend supports mapping between LDAP and keystone user
  attributes via the 'user_<attribute_name>_attribute' settings in the
  ldap driver configuration.

  The implementation is incomplete, since there is no support for
  specifying a 'user_description_attribute' setting.

  As long as the LDAP attribute name is 'description', one could specify
  a 1:1 'user_additional_attribute_mapping = description:description'
  mapping as a workaround, which would yield the desired result.

  In case a users full name is stored in a different attribute (as with
  many AD backends where the users full name is contained in the
  'displayName' attribute) there is no way to specify this mapping and
  results in users having no description.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1542417/+subscriptions