Repository navigation
docs(api): issuer binding, scopes, and wallet sign-in - #11
Conversation
Four changes to how ACTA credentials work, now that the API carries them. Issuance binds the `issuer`, not the `owner`. The old text described the previous behaviour, where binding the recipient meant a standard key could only issue credentials to itself. Reads and moves still bind `owner`, which is correct there. Scopes let a key be narrowed (issue without read, and so on). Records that a key with no scopes is unrestricted, so nothing issued earlier changed. Wallet sign-in is documented as the credential browsers should prefer, with why it is stronger than a bearer key: a session can only be minted by whoever controls the wallet. API keys stay the right answer for servers.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (3)
📝 WalkthroughWalkthroughThe API reference now separates vault ownership checks from issuer authorization. Issuance binds API keys to ChangesAuthentication documentation
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Documents the four changes just landed in acta-api (#108, #109, #110, #111), in en/es/fr.
owner, which is correct there.Summary by CodeRabbit