Skip to content

[CloudFoundry Auth] Issue with providing access to a whole organisation #9052

@Kump3r

Description

@Kump3r

Summary

While working on Switching to CloudFoundry v3 API, we noticed that,
when setting a team with --cf-org=ORG_NAME, or respective configuration file (documentation), members of that organisation are not able to see the the team/pipeline contents in Concourse.

Steps to reproduce

  1. Set a team with cf ORG only
  2. Assign users to the respective ORG in CloudFoundry
  3. Login to this team with your CF user.

Expected results

Team and pipelines are visible UI. Access granted FLY.

Actual results

Team and pipelines are missing UI . No access FLY.
Screenshot with problem:
CF all org issue

Additional context

Perhaps as no one has complained about this, I suspect this is not widely used and it can be considered for deprecation

Triaging info

  • Concourse version: Not sure when this broke, but newer releases lack the feature.
  • Browser (if applicable): N/A
  • Did this used to work? Not sure, I am guessing since it is in the codebase, it used to work at a certain point in the past.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions