[api] /v3/policy incorrectly shows user_id and project_id as supported parameters
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Low
|
Steve Martinelli | ||
openstack-api-site |
Fix Released
|
High
|
Diane Fleming |
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://
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.
description: | updated |
Changed in keystone: | |
assignee: | nobody → jiaxi (tjxiter) |
Changed in keystone: | |
assignee: | jiaxi (tjxiter) → nobody |
Changed in openstack-api-site: | |
status: | Incomplete → Triaged |
importance: | Medium → High |
Changed in openstack-api-site: | |
assignee: | nobody → Diane Fleming (diane-fleming) |
status: | Triaged → Confirmed |
Changed in keystone: | |
assignee: | nobody → guoshan (guoshan) |
tags: | added: api-ref |
summary: |
- Policy related operations of Identity v3 API in API Complete Reference - need modification. + [api] /v3/policy incorrectly shows user_id and project_id as supported + parameters |
Changed in keystone: | |
milestone: | none → ocata-1 |
The Policy API in Keystone is very rough and not really usable at the moment (since you can only store blobs of data referenced by a policy_id). We are working to address these issues in this next cycle with significant enhancements. The API site is likely out of date on the keystone policy api as it has never seen real adoption.
I'm going to mark this as a doc bug and something we should look at addressing as we update the policy API and handling in Keystone during liberty.