yahoo-eng-team team mailing list archive

[Darren Hague <d.hague@xxxxxxx>]

Public bug reported:

The OpenStack Identity v3 API documentation
(http://developer.openstack.org/api-ref-identity-v3.html) has incorrect
examples of how to format EC2 credentials.

The documentation says to use 
  blob: { "access":"--access key--", "secret":"--secret key--"}
but Keystone rejects this with a 400 error.

The value of blob must actually be a string value, and the JSON for access & secret keys is encoded within this string:
  "blob": "{\"access\":\"--access-key--\",\"secret\":\"--secret-key--\"}"

** Affects: keystone
     Importance: Undecided
     Assignee: Darren Hague (dhague)
         Status: In Progress


** Tags: documentation

** Changed in: keystone
     Assignee: (unassigned) => Darren Hague (dhague)

** Changed in: keystone
       Status: New => In Progress

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

Title:
  v3 API doc: credentials blob content should be JSON-in-a-string
  instead of actual JSON

Status in OpenStack Identity (Keystone):
  In Progress

Bug description:
  The OpenStack Identity v3 API documentation
  (http://developer.openstack.org/api-ref-identity-v3.html) has
  incorrect examples of how to format EC2 credentials.

  The documentation says to use 
    blob: { "access":"--access key--", "secret":"--secret key--"}
  but Keystone rejects this with a 400 error.

  The value of blob must actually be a string value, and the JSON for access & secret keys is encoded within this string:
    "blob": "{\"access\":\"--access-key--\",\"secret\":\"--secret-key--\"}"

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