paritytech / paritytech/web3-storage
Address L0/L1 mismatch for api endpoints
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 12
- Forks
- 3
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 33
Description
See this comment: https://github.com/paritytech/web3-storage/pull/215#discussion_r3453465484
Basically /node GET, /read, /fetch_nodes and /exists are RequiredRole::Reader on L1 but role is unchecked on L0. Decide, whether we should have the reader role at all.
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.
Research direction
Read the linked pull request discussion first, then inspect the authorization handling for the /node GET, /read, /fetch_nodes, and /exists endpoints on L0 and L1. Done means reaching and documenting a decision about whether these endpoints require the reader role and aligning their behavior across both layers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, authorization
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100