v3 credentials get blob format inconsistent

[Steven Hardy]

The v3/credentials API specifies the blob response to be json, but due to bug #1259584, any credentials stored via the ec2tokens extension will incorrectly return a dict.

This makes it hard for clients (and in particular users migrating from ec2tokens to v3/credentials) to handle the blob data consistently as you don't know what format you're going to get.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/66974

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/66974
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=6a051c19817292f4e221759f80d0b298aebbcee1
Submitter: Jenkins
Branch: master

commit 6a051c19817292f4e221759f80d0b298aebbcee1
Author: Steven Hardy <email address hidden>
Date: Wed Jan 15 21:47:52 2014 +0000

    v3 credentials, ensure blob response is json

    The v3/credentials API specifies the blob response to be json, but
    due to bug #1259584, any credentials stored via the ec2tokens extension
    will incorrectly return a dict. This makes it hard for clients (and
    in particular users migrating from ec2tokens to v3/credentials) to
    handle the blob data consistently, so add a workaround to ensure the
    response is always serialized as json if the existing DB contents is
    a dict instead of a json string.

    Change-Id: I340cdf4e565fdadacb41b39acace3948aafb9b92
    Related-Bug: #1259584
    Closes-Bug: #1269637