yahoo-eng-team team mailing list archive

[Steve Martinelli <1622806@xxxxxxxxxxxxxxxxxx>]

The way the bug is initially written is very much an opinion, I don't
see a bug in the message, just a preference that the "blob" attribute be
turned into a proper JSON dict.

Unfortunately, this isn't possible due to breaking API contracts and
backwards compatibility.

Further, this is as-designed, dating way back to the first v3
implementation:
https://github.com/openstack/keystone/commit/ddc8c833684ff0db65553b09b87eed7b80c7075d
#diff-d36d696b43e6991c5e56b7085e3ca411R56

The credentials backend saves a variety of different credentials (ec2,
totp, and generic keys), and the "blob" is used because of that, so
users can always look at the blob attribute, rather than a credential
specific one.

Why is calling json.loads() not an option?

** Changed in: keystone
       Status: New => Opinion

-- 
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/1622806

Title:
  v3 Credential APIs return credential in blob attribute as string
  instead of json object

Status in OpenStack Identity (keystone):
  Opinion

Bug description:
  v3 Credential APIs return credential in blob attribute but that is
  return as string instead of json object.

  Returning actual dict object as string in API is not much comfortable
  to use for users and seems like wrong type in response.

  credential in 'blob' attribute should be de serialized before
  returning and users can get the same as json object.

  ref- http://developer.openstack.org/api-ref/identity/v3/?expanded
  =create-credential-detail

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