yahoo-eng-team team mailing list archive

[Dolph Mathews <904529@xxxxxxxxxxxxxxxxxx>]

Marking this as wont-fix because A) we can't really change that API
anymore, and B) v3 has been implemented with a /v3/credentials API,
which is (in part) intended to replace the EC2 v2 extension along with
pluggable auth (we also haven't implemented an ec2 plugin yet). The
above google doc has moved to git and is currently published at:

  https://github.com/openstack/identity-api/blob/master/openstack-
identity-api/src/markdown/identity-api-v3.md

** Changed in: keystone
       Status: Triaged => Won't Fix

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

Title:
  Schema of ec2tokens is incompatible with XML

Status in OpenStack Identity (Keystone):
  Won't Fix

Bug description:
  ec2tokens currently serializes the request values as a dictionary with
  keys  as the equivalent of XML elements.  For XML, we would need
  <params><param key="A" value="AValue" />... or similar...

  Currently we have this:
  {"ec2Credentials": {"access": "e51d453d-e88d-ed8d-886f-f7f91f111a2d", "host": "192.168.1.104:8773", "verb": "POST", "params": {"SignatureVersion": "2", "AWSAccessKeyId": "e51d453d-e88d-ed8d-886f-f7f91f111a2d", "Timestamp": "2011-12-14T00:41:10Z", "SignatureMethod": "HmacSHA256", "Version": "2011-01-01", "Action": "DescribeInstances"}, "signature": "7V3HY0MlPnkxOJ7eNULbA9CiAGkO4ON9EHfVQeeIRq0=", "path": "/services/Cloud/"}}

  Then given that we need this for XML, sanity dictates that we follow the comparable schema for JSON i.e.
  params : [ { key: 'A', value: 'AValue' }, { key: 'B', value: 'BValue' } ...]

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