cloudfoundry / cloudfoundry/cloud_controller_ng
`v3/Roles` regression in functionality migration from V2
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 207
- Forks
- 373
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 56
Description
Thanks for submitting an issue to cloud_controller_ng. We are always trying to improve! To help us, please fill out the following template.
Issue
V3 migration: Lost functionality to remove your own Org roles without the Org Manager role.
Context
DELETE /v2/organizations/:guid/:type/:uaaGuid allows you to delete yourself. EG: removing your own Org User role without having Org Manager roles.
Using DELETE /v3/roles/:guid this is no longer the case.
Steps to Reproduce
Using V3:
- Have the Org User role or Org Auditor without the Org Manager role.
- Try to delete the Org User or Org Auditor role.
Expected result
Allows you to delete the Role normally
Current result
Returns with error: "You are not authorized to perform the requested action"
CF curl error screenshot
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the V3 DELETE /v3/roles/:guid entry point and its authorization checks, then compare the behavior with DELETE /v2/organizations/:guid/:type/:uaaGuid. Reproduce the Org User and Org Auditor self-removal cases without the Org Manager role; done means those requests succeed without the authorization error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- api, authorization
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100