paritytech / paritytech/host-rust-core
RFC: Credential-endpoint remote permission
Open
Product permissions
rfc
- Dominant language
- Swift
- Stars
- 10
- Forks
- 3
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 148
Description
Source PR: #335 · docs/rfcs/0025-scoped-remote-permission.md · @BigTava
Description
A Credential { domain, path, method } variant of RemotePermission grants outbound access to one endpoint, and the host attaches a ring VRF personhood proof to every request the grant covers.
Motivation
A product cannot hold a server-side API key, and Remote is too coarse either to approve a single endpoint or to prove that a stable person is behind the call.
Requirements
- The variant is appended last, so stored permission keys stay valid.
- One
(domain, path, method)triple per grant, https only, no wildcards. - Denied without a session or people-set membership; the prompt names the endpoint and the alias disclosure.
- Every covered request carries
X-Polkadot-Proof,-Ring,-Timestampand-Nonce.
Tasks
- RFC document body
- Implementation — rust-core
- Implementation — hosts
- dotli
- Desktop
- iOS
- Android
- host-cli
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.
Assessment
This issue has not been assessed yet.