← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1448602] [NEW] Policy related operations of Identity v3 API in API Complete Reference need modification.

 

Public bug reported:

Recently, when I was trying to construct policy related HTTP requests
according to the API Complete Reference's Identity v3 API page, the
requests I constructed are not accepted by Keystone.

So I used openstackclient to do what I want and got the network packets
using wireshark. Then I found that the correct requests and responses
are actually not the ones recorded in API Complete Reference.

For example, in order to create a policy, the API details showed in API
Complete Reference: http://developer.openstack.org/api-ref-
identity-v3.html#createPolicy  indicates that "project_id" and "user_id"
are needed, while actually they are not! The HTTP requests constructed
by openstackclient are same with those in API guide of Keystone, still,
taking policy creation as an example,
http://specs.openstack.org/openstack/keystone-specs/api/v3/identity-
api-v3.html#create-policy

Thus, I think that the policy related API reference in API Complete
Reference is out dated and should be modified according to Keystone's
api specs.

** Affects: keystone
     Importance: Undecided
         Status: New

** Affects: openstack-api-site
     Importance: Undecided
         Status: New

** Description changed:

  Recently, when I was trying to construct policy related HTTP requests
  according to the API Complete Reference's Identity v3 API page, the
  requests I constructed are not accepted by Keystone.
  
  So I used openstackclient to do what I want and got the network packets
  using wireshark. Then I found that the correct requests and responses
  are actually not the ones recorded in API Complete Reference.
  
  For example, in order to create a policy, the API details showed in API
  Complete Reference: http://developer.openstack.org/api-ref-
  identity-v3.html#createPolicy  indicates that "project_id" and "user_id"
- is needed, while actually they are not! The HTTP requests constructed by
- openstackclient are same with those in API guide of Keystone, still,
+ are needed, while actually they are not! The HTTP requests constructed
+ by openstackclient are same with those in API guide of Keystone, still,
  taking policy creation as an example,
  http://specs.openstack.org/openstack/keystone-specs/api/v3/identity-
  api-v3.html#create-policy
  
  Thus, I think that the policy related API reference in API Complete
  Reference is out dated and should be modified according to Keystone's
  api specs.

** Also 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/1448602

Title:
  Policy related operations of Identity v3 API in API Complete Reference
  need modification.

Status in OpenStack Identity (Keystone):
  New
Status in OpenStack API documentation site:
  New

Bug description:
  Recently, when I was trying to construct policy related HTTP requests
  according to the API Complete Reference's Identity v3 API page, the
  requests I constructed are not accepted by Keystone.

  So I used openstackclient to do what I want and got the network
  packets using wireshark. Then I found that the correct requests and
  responses are actually not the ones recorded in API Complete
  Reference.

  For example, in order to create a policy, the API details showed in
  API Complete Reference: http://developer.openstack.org/api-ref-
  identity-v3.html#createPolicy  indicates that "project_id" and
  "user_id" are needed, while actually they are not! The HTTP requests
  constructed by openstackclient are same with those in API guide of
  Keystone, still, taking policy creation as an example,
  http://specs.openstack.org/openstack/keystone-specs/api/v3/identity-
  api-v3.html#create-policy

  Thus, I think that the policy related API reference in API Complete
  Reference is out dated and should be modified according to Keystone's
  api specs.

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


Follow ups

References