yahoo-eng-team team mailing list archive

[OpenStack Infra <1413627@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/149330
Committed: https://git.openstack.org/cgit/openstack/api-site/commit/?id=dd38f4b31b1e1fada0f64bba5ea4a192914f6769
Submitter: Jenkins
Branch:    master

commit dd38f4b31b1e1fada0f64bba5ea4a192914f6769
Author: Darren Hague <d.hague@xxxxxxx>
Date:   Thu Jan 22 15:36:08 2015 +0000

    credentials blob content corrected to be JSON-in-a-string
    
    Corrected the JSON examples for the Identity /v3/credentials endpoint
    and updated the explanatory text accordingly.
    
    Change-Id: I2931c21d0460a644eb421ebfdc5d1626d20d6618
    Closes-Bug: 1413627


** Changed in: openstack-api-site
       Status: In Progress => 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/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
Status in OpenStack API documentation site:
  Fix Released

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