cloudfoundry / cloudfoundry/cloud_controller_ng

User with Org Auditor role can't see all spaces across the ORG

Open
#2,333 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

unscheduled
Dominant language
Ruby
Stars
207
Forks
373
Avg merge
2d 12h
Merged PRs (30d)
56

Description

History

Initially submitted to https://github.com/cloudfoundry/docs-cloudfoundry-concepts/issues/156 but then it was moved to slack at https://app.slack.com/client/T02FL4A1X/C07C04W4Q/thread/C07C04W4Q-1621450296.008000.

Issue

Our use case, we want a single user with ORG auditor role to be able to retrieve all the events for an ORG (doable now) and to be able to take the SPACE GUID for each event to get the SPACE NAME to include it in our daily "event report". Do to the SPACE NAME part now, we have to remember to add the user account to every space.

Expected result

We'd want an ORG auditor to be able to see all SPACE names in the ORG .

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with issue #2333 and review the linked Slack thread, since the discussion was moved there from the documentation issue. Determine how an ORG auditor currently retrieves events and resolves space GUIDs, then define the permission change needed so all space names in the organization are visible; done means the expected report use case works without adding the user to each space.

Written by the indexing model from the issue text.

Assessment

Tech stack
ruby
Domain
authorization
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.