[Yahoo-eng-team] [Bug 1293698] Re: Can't map user description using LDAP
** Changed in: keystone Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1293698 Title: Can't map user description using LDAP Status in OpenStack Identity (Keystone): Fix Released Status in Keystone icehouse series: Fix Released Bug description: There's no way to set a mapping for the description attribute. First, there's no user_desc_attribute config option (there's a tenant_desc_attribute), although there doesn't need to be, but Second, if you try to set user_additional_attribute_mapping=description:description the server ignores it. The log says: WARNING keystone.common.ldap.core [-] Invalid additional attribute mapping: description:description. Value description must use one of password, enabled, default_project_id, name, email. Why only allow the attributes that keystone knows about? Those attributes already have user_*_attribute config options anyways! Third, when keystone gets the users, it doesn't include the extra attr mapping attrs. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1293698/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1293698] Re: Can't map user description using LDAP
** Changed in: keystone/icehouse Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1293698 Title: Can't map user description using LDAP Status in OpenStack Identity (Keystone): Fix Committed Status in Keystone icehouse series: Fix Released Bug description: There's no way to set a mapping for the description attribute. First, there's no user_desc_attribute config option (there's a tenant_desc_attribute), although there doesn't need to be, but Second, if you try to set user_additional_attribute_mapping=description:description the server ignores it. The log says: WARNING keystone.common.ldap.core [-] Invalid additional attribute mapping: description:description. Value description must use one of password, enabled, default_project_id, name, email. Why only allow the attributes that keystone knows about? Those attributes already have user_*_attribute config options anyways! Third, when keystone gets the users, it doesn't include the extra attr mapping attrs. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1293698/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1293698] Re: Can't map user description using LDAP
** Also affects: keystone/icehouse Importance: Undecided Status: New ** Changed in: keystone/icehouse Status: New = In Progress ** Changed in: keystone/icehouse Importance: Undecided = Wishlist ** Changed in: keystone/icehouse Assignee: (unassigned) = Brant Knudson (blk-u) ** Changed in: keystone/icehouse Milestone: None = 2014.1.1 ** Tags removed: icehouse-backport-potential -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1293698 Title: Can't map user description using LDAP Status in OpenStack Identity (Keystone): Fix Committed Status in Keystone icehouse series: In Progress Bug description: There's no way to set a mapping for the description attribute. First, there's no user_desc_attribute config option (there's a tenant_desc_attribute), although there doesn't need to be, but Second, if you try to set user_additional_attribute_mapping=description:description the server ignores it. The log says: WARNING keystone.common.ldap.core [-] Invalid additional attribute mapping: description:description. Value description must use one of password, enabled, default_project_id, name, email. Why only allow the attributes that keystone knows about? Those attributes already have user_*_attribute config options anyways! Third, when keystone gets the users, it doesn't include the extra attr mapping attrs. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1293698/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
