yahoo-eng-team team mailing list archive

[Brant Knudson <bknudson@xxxxxxxxxx>]

Public bug reported:


If you create a consumer with some weird field like "some:wierd-field", the name of the field gets normalized to "some_wierd_field". But when you try to update that field with "some:wierd-field", the name doesn't get normalized, so it creates a new field with the wierd name rather than updating the originally normalized field.

The field name should be normalized on update just like it is on create.

** Affects: keystone
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1276857

Title:
  update oauth consumer fields not normalized

Status in OpenStack Identity (Keystone):
  New

Bug description:
  
  If you create a consumer with some weird field like "some:wierd-field", the name of the field gets normalized to "some_wierd_field". But when you try to update that field with "some:wierd-field", the name doesn't get normalized, so it creates a new field with the wierd name rather than updating the originally normalized field.

  The field name should be normalized on update just like it is on
  create.

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