Error for Keystone V3 extension "OS-SIMPLE-CERT" for XML interface

Bug #1311573 reported by meenakshi m
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Identity (keystone)
Won't Fix
Low
Unassigned

Bug Description

I tried to execute keystone V3 API "OS-SIMPLE-CERT/certificates" for xml interface using curl request.

The response of the curl request doesnt contain a status code and an error message is observed.

-Below is the curl command used:

 curl -i -X GET http://127.0.0.1:35357/v3/OS-SIMPLE-CERT/certificates
 -H "Content-Type: application/xml" -H "Accept: application/xml" -H "User-Agent: python-keystoneclient"
 -H "X-Auth-Token: <Token-Omitted>"

-Below is the response:

  Output:
  HTTP/1.1 None None
  Vary: X-Auth-Token
  Content-Type: application/json
  Content-Length: 4384
  Date: Thu, 17 Apr 2014 07:06:07 GMT

  {"error": {"message": "Certificate:\n Data:\n Version:
           3 (0x2)\n Serial Number: 1 (0x1)\n
           Signature Algorithm: sha1WithRSAEncryption\n
           Issuer: C=US, ST=Unset, L=Unset, O=Unset, CN=www.example.com\n
           Validity\n Not Before: Apr 17 06:58:08 2014 GMT\n
           Not After : Apr 14 06:58:08 2024 GMT\n Subject: C=US,
           ST=Unset, O=Unset, CN=www.example.com\n Subject Public Key Info:\n
           Public Key Algorithm: rsaEncryption\n Public-Key: (2048 bit)\n
           Modulus:\n 00:db:f2:8d:33:10:a3:b7:5a:c9:6e:58:a1:c9:2b:\n
           89:f2:d2:2d:88:a7:73:a4:da:48:3e:2b:57:2e:99:\n
           51:a8:73:26:5c:a0:54:32:1f:ad:35:8a:5a:65:2b:\n
           22:13:18:9f:66:ac:09:0b:31:60:21:80:2f:af:5e:\n
           03:7e:e0:66:8d:9d:b8:2e:87:82:ca:74:ee:b5:92:\n
           4c:d8:f5:c9:33:c1:de:fe:29:c7:2e:ac:7d:10:8e:\n
           57:27:27:36:b2:70:d5:d5:e0:be:7f:b6:68:af:e5:\n
           a8:17:94:25:3e:80:69:c8:ad:72:c9:ce:b5:3a:d9:\n
           71:f3:fd:45:50:2e:8f:c2:43:65:34:98:03:ee:14:\n
           60:82:30:f7:14:85:2d:cb:5c:d4:92:55:e6:81:1e:\n
           9f:93:df:3e:dc:3b:ad:0d:54:84:e1:48:20:73:42:\n
           63:c0:54:4e:7b:e3:f3:70:97:f2:d6:ac:2e:33:c8:\n
           4f:d1:9d:ef:a5:36:c5:d0:0b:19:d2:5f:3f:08:88:\n
           f5:bf:44:57:88:c2:23:87:b6:42:7e:0d:3d:6b:b2:\n
           a9:a1:56:5d:8a:20:c2:5d:b2:7f:01:ee:1f:5a:ee:\n
           b7:ff:38:02:e6:bf:a8:ad:cc:3a:bd:18:6c:1b:b9:\n
           c1:eb:d4:50:58:4a:49:fd:52:64:4b:a9:92:80:7b:\n
           9d:95\n Exponent: 65537 (0x10001)\n
           X509v3 extensions:\n X509v3 Basic Constraints: \n
           CA:FALSE\n X509v3 Subject Key Identifier: \n
           75:B4:09:04:09:5A:50:70:F6:15:E7:1F:D0:ED:26:7E:2A:7D:AF:7B\n
           X509v3 Authority Key Identifier: \n
           keyid:62:CC:B7:5A:72:BB:A0:7D:47:03:62:6B:6E:05:B0:FB:E6:1A:88:EE\n\n
           Signature Algorithm: sha1WithRSAEncryption\n
           4a:20:15:6d:70:09:6f:a6:7d:e7:8c:6a:26:77:e3:57:33:34:\n
           b9:53:06:da:4e:76:3e:83:7c:79:c1:cf:aa:36:d9:05:c5:2f:\n
           1f:81:44:ec:19:40:25:91:1f:cb:99:51:93:93:f1:6c:61:32:\n
           0d:9e:a9:ce:e9:a7:30:43:a8:a8:7b:96:35:ea:e3:59:f9:df:\n
           f1:f8:48:e0:7b:36:eb:c4:ae:c7:1d:13:aa:be:9a:79:c5:ba:\n
           89:5d:bb:3c:4f:ea:73:c4:1f:96:e1:c8:19:f4:1e:06:50:cb:\n
           75:dd:ed:95:d6:02:1d:08:2b:73:82:24:68:7a:c6:91:f8:06:\n
           58:f5:f9:ff:6c:7b:40:8a:0c:f9:11:e9:a2:d7:46:bb:f8:74:\n
           78:29:46:aa:c2:86:10:7c:48:7f:90:57:82:85:a2:f5:53:25:\n
           97:c5:4a:83:10:db:22:d8:9a:c4:7c:a3:bc:3d:9d:f0:d0:9f:\n
           fd:d5:4c:e4:74:3b:74:9c:73:f1:74:0b:b9:1a:31:a5:17:b1:\n
           4b:fa:94:ee:f0:f4:34:0f:40:56:b7:6a:69:96:b7:8a:83:5e:\n
           11:00:22:06:c1:3b:82:25:cd:1b:4b:88:0d:34:f8:af:2d:7b:\n
           27:4d:74:ea:ee:6a:25:dc:1d:64:a1:5d:75:1f:4c:8f:f5:76:\n
          6d:af:cd:06\n
          -----BEGIN CERTIFICATE-----\n
          MIIDZjCCAk6gAwIBAgIBATANBgkqhkiG9w0BAQUFADBXMQswCQYDVQQGEwJVUzEO\n
          MAwGA1UECAwFVW5zZXQxDjAMBgNVBAcMBVVuc2V0MQ4wDAYDVQQKDAVVbnNldDEY\n
          MBYGA1UEAwwPd3d3LmV4YW1wbGUuY29tMB4XDTE0MDQxNzA2NTgwOFoXDTI0MDQx\n
          NDA2NTgwOFowRzELMAkGA1UEBhMCVVMxDjAMBgNVBAgMBVVuc2V0MQ4wDAYDVQQK\n
          DAVVbnNldDEYMBYGA1UEAwwPd3d3LmV4YW1wbGUuY29tMIIBIjANBgkqhkiG9w0B\n
          AQEFAAOCAQ8AMIIBCgKCAQEA2/KNMxCjt1rJblihySuJ8tItiKdzpNpIPitXLplR\n
          qHMmXKBUMh+tNYpaZSsiExifZqwJCzFgIYAvr14DfuBmjZ24LoeCynTutZJM2PXJ\n
          M8He/inHLqx9EI5XJyc2snDV1eC+f7Zor+WoF5QlPoBpyK1yyc61Otlx8/1FUC6P\n
          wkNlNJgD7hRggjD3FIUty1zUklXmgR6fk98+3DutDVSE4Uggc0JjwFROe+PzcJfy\n
          1qwuM8hP0Z3vpTbF0AsZ0l8/CIj1v0RXiMIjh7ZCfg09a7KpoVZdiiDCXbJ/Ae4f\n
          Wu63/zgC5r+orcw6vRhsG7nB69RQWEpJ/VJkS6mSgHudlQIDAQABo00wSzAJBgNV\n
          HRMEAjAAMB0GA1UdDgQWBBR1tAkECVpQcPYV5x/Q7SZ+Kn2vezAfBgNVHSMEGDAW\n
          gBRizLdacrugfUcDYmtuBbD75hqI7jANBgkqhkiG9w0BAQUFAAOCAQEASiAVbXAJ\n
          b6Z954xqJnfjVzM0uVMG2k52PoN8ecHPqjbZBcUvH4FE7BlAJZEfy5lRk5PxbGEy\n
          DZ6pzumnMEOoqHuWNerjWfnf8fhI4Hs268Suxx0Tqr6aecW6iV27PE/qc8QfluHI\n
          GfQeBlDLdd3tldYCHQgrc4IkaHrGkfgGWPX5/2x7QIoM+RHpotdGu/h0eClGqsKG\n
          EHxIf5BXgoWi9VMll8VKgxDbItiaxHyjvD2d8NCf/dVM5HQ7dJxz8XQLuRoxpRex\n
          S/qU7vD0NA9AVrdqaZa3ioNeEQAiBsE7giXNG0uIDTT4ry17J0106u5qJdwdZKFd\n
          dR9Mj/V2ba/NBg==\n
          -----END CERTIFICATE-----\n",
          "code": null, "title": null}}

The same curl request worked fine for json interface.

Submitted a patch for "OS-SIMPLE-CERT/certificates" for Json Interface.
Please Refer: https://review.openstack.org/#/c/87750/

Can anyone clarify whether xml interface is there are not , ASAP.

- Regards,
   Meenakshi M

Revision history for this message
Dolph Mathews (dolph) wrote :

There's neither an XML interface nor a JSON interface to this call.

The only supported content type on this call is "application/x-pem-file". The content of of the error->message attribute in your example response should be the entire response body itself, regardless of whether the client demands an application/xml response or not.

The XML translation layer is also deprecated as of Icehouse, due to the high cost of maintenance and a lack of interest in the community to support it (hence the Won't Fix).

Changed in keystone:
importance: Undecided → Low
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.