yahoo-eng-team team mailing list archive

[Andrea Frittoli <1267544@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

The response to the token API in the v2 API is not consistent between
JSON and XML

In JSON the format is as follows:

        "serviceCatalog": [
            {
                "endpoints": [
                    {
                        "adminURL": "http://127.0.0.1:8774/v2/aff91593f7fb43cc863a34cf718584cb";,
                        "id": "1f61239858ba4fc595284473a05c79a9",
                        "internalURL": "http://127.0.0.1:8774/v2/aff91593f7fb43cc863a34cf718584cb";,
                        "publicURL": "http://127.0.0.1:8774/v2/aff91593f7fb43cc863a34cf718584cb";,
                        "region": "RegionOne"
                    }
                ],
                "endpoints_links": [],
                "name": "nova",
                "type": "compute"
            },


While in XML the format is:

  <serviceCatalog>
    <service type="compute" name="nova">
      <endpoints_links/>
      <endpoint adminURL="http://127.0.0.1:8774/v2/8bae6214d4314a0aa1d5dce34c7a5f38"; region="RegionOne" publicURL="http://127.0.0.1:8774/v2/8bae6214d4314a0aa1d5dce34c7a5f38"; internalURL="http://127.0.0.1:8774/v2/8bae6214d4314a0aa1d5dce34
c7a5f38" id="1f61239858ba4fc595284473a05c79a9"/>
    </service>

So it's "endpoints" for JSON and "endpoint" for XML.

** 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/1267544

Title:
  List of endpoints in v2 token response is "endpoint" in XML

Status in OpenStack Identity (Keystone):
  New

Bug description:
  The response to the token API in the v2 API is not consistent between
  JSON and XML

  In JSON the format is as follows:

          "serviceCatalog": [
              {
                  "endpoints": [
                      {
                          "adminURL": "http://127.0.0.1:8774/v2/aff91593f7fb43cc863a34cf718584cb";,
                          "id": "1f61239858ba4fc595284473a05c79a9",
                          "internalURL": "http://127.0.0.1:8774/v2/aff91593f7fb43cc863a34cf718584cb";,
                          "publicURL": "http://127.0.0.1:8774/v2/aff91593f7fb43cc863a34cf718584cb";,
                          "region": "RegionOne"
                      }
                  ],
                  "endpoints_links": [],
                  "name": "nova",
                  "type": "compute"
              },

  
  While in XML the format is:

    <serviceCatalog>
      <service type="compute" name="nova">
        <endpoints_links/>
        <endpoint adminURL="http://127.0.0.1:8774/v2/8bae6214d4314a0aa1d5dce34c7a5f38"; region="RegionOne" publicURL="http://127.0.0.1:8774/v2/8bae6214d4314a0aa1d5dce34c7a5f38"; internalURL="http://127.0.0.1:8774/v2/8bae6214d4314a0aa1d5dce34
  c7a5f38" id="1f61239858ba4fc595284473a05c79a9"/>
      </service>

  So it's "endpoints" for JSON and "endpoint" for XML.

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