Implement Tier-2 Data Proxying for Legacy Backends
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- api, authentication, authorization, backend, security
Research direction
Start by reading ADRs 0008, 0010, and 0021 to understand the Tier-2 access model and physical data endpoints. Locate the API entry point for datasets and determine how authentication, FDS authorisation, and remote data access are currently handled. Done means a GET /datasets/{id}/proxy flow authenticates and authorises the user, fetches Tier-2 data with internal credentials, and streams the binary response.
Written by the indexing model from the issue text.
Description
FDS successfully implements "Tier-1" direct data access via cloud-native Credential Vending (S3/Zarr). However, the architecture also defines a requirement to support legacy "Tier-2" data resting on systems that do not support modern token exchange (FTP servers, internal HTTP endpoints, basic NAS mounts).
Acceptance Criteria:
- Implement a new
GET /datasets/{id}/proxyendpoint mechanism. - The API must authenticate the user, validate authorisation against the FDS database, and then independently fetch the remote Tier-2 data using internal service credentials.
- The API must stream the binary data back to the client.
Governing ADR(s): ADR 0008, ADR 0010, ADR 0021
Migrated from the internal tracker, where it was #3, opened 2026-02-25.
- Dominant language
- Python
- Stars
- 0
- Forks
- 1
- Avg merge
- 26m
- Merged PRs (30d)
- 24
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.
More from ukaea/fds
-
performance
Difficulty 4/5 3-5 days Newbie friendliness 52/100
-
api architecture feature metadata priority: high
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
architecture metadata priority: medium
Difficulty 5/5 Over a week Newbie friendliness 30/100
-
enhancement fair-compliance metadata priority: medium
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Consume external provenance: inverse PROV mapping to register upstream inputs + create a Collection Openapi fair-compliance feature metadata priority: medium
Difficulty 5/5 Over a week Newbie friendliness 35/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100