Do we really need to RBAC protect version resource
Bug #1290445 reported by
Arvind Tiwari
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Barbican |
Fix Released
|
High
|
Arvind Tiwari |
Bug Description
Barbican does RBAC check for version call, which does not seems correct behavior.
We should should remove the RBAC check for the version call.
Changed in barbican: | |
assignee: | nobody → Arvind Tiwari (arvind-tiwari) |
Changed in barbican: | |
milestone: | none → icehouse |
importance: | Undecided → High |
Changed in barbican: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I don't think we need the version call protected. I think though if we are to remove the protection on the endpoint then we should adopt the OpenStack way of handling API versions, http:// docs.openstack. org/api/ openstack- compute/ 2/content/ Versions- d1e1193. html#d6e808
Thoughts?