source-cooperative / source-cooperative/source.coop

Epic: Access Controls

Open
#267 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

epic
Dominant language
TypeScript
Stars
26
Forks
9
Avg merge
1d 7h
Merged PRs (30d)
42

Description

Access Controls

Epic tracking the implementation of authenticated read/write access to data products through the Source Cooperative data proxy.

This work implements the architecture described in data.source.coop RFC-001, including OIDC-based identity federation, Role-based access scoping via an STS endpoint, and authenticated connections to upstream storage backends.

Key Design Documents
  • ADR-001: S3 API Compatibility and Temporary Credentials
  • ADR-004: Inbound Authentication — OIDC Federation and Role-Based STS Exchange
  • ADR-005: Authorization Model — Role Ceiling with Dynamic Account Permission Resolution
  • ADR-006: Outbound Connectivity — OIDC Issuer Model
Sub-issues
  • Integrate Roles in data.source.coop
  • Create STS endpoint for temporary credentials in data.source.coop
  • Add admin interface for Roles in source.coop
  • Support external OIDC Identity Providers
  • Connect to backends with auth credentials (data proxy as OIDC provider)
  • Enable uploads, multipart uploads, and deletes on data.source.coop
  • Identity Provider admin tooling on source.coop
  • Use data proxy for multipart uploads from the browser

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 by reading RFC-001 and ADR-001, ADR-004, ADR-005, and ADR-006, then review the listed sub-issues. The work is complete when the access-control capabilities tracked by those sub-issues are implemented across the data proxy and source.coop interfaces.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
api, authentication, authorization, backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.