Skip to content
This repository was archived by the owner on Sep 30, 2024. It is now read-only.
This repository was archived by the owner on Sep 30, 2024. It is now read-only.

Implement Role-Based Access Control (Tracking) #43276

Closed
Closed
Implement Role-Based Access Control (Tracking)#43276
Assignees
BolajiOlajide
Labels
rbactracking
@BolajiOlajide

Description

@BolajiOlajide
BolajiOlajide
opened on Oct 21, 2022

Problem statement

Customers expect us to have the authorization on the API implemented (product gap “Interservice authentication” from one of the customers). This is standard across the industry but we are not enforcing it.
Not being able to define fine-grained access to several resources limits customers from enabling some features on Sourcegraph like Batch Changes, because they don’t want just anyone to be able to make bulk code changes across multiple repositories.

Problem validation / why

Some customers are blocked from enabling features like Batch Changes because we don't have an access control system.
Examples of customers that are currently blocked:

There's no way we're going to give x,000 engineers the ability to deploy changes across all our repositories

See RFC 747 Role-Based Access Control for current candidate

Tracked issues

@unassigned

Completed

@BolajiOlajide

Completed

@courier-new

Completed

@github-actions

Completed

Legend

  • 👩 Customer issue
  • 🐛 Bug
  • 🧶 Technical debt
  • 🎩 Quality of life
  • 🛠️ Roadmap
  • 🕵️ Spike
  • 🔒 Security issue
  • 🙆 Stretch goal

/cc @sourcegraph/iam

Metadata

Metadata

Assignees

Labels

rbactracking

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions