docs: document directed identity for non-interactive grants#777
docs: document directed identity for non-interactive grants#777
Conversation
Updated client-keys.mdx, grants.mdx, and auth.mdx to reflect updates to OP specifications
✅ Deploy Preview for openpayments ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
melissahenderson
left a comment
There was a problem hiding this comment.
Looks good overall. Do you think we should add directed identity to the glossary?
|
|
||
| :::tip[Summary] | ||
| Client keys are unique identifiers that allow clients to sign Open Payments requests. They allow a client's identity to be verified through a public key registry. | ||
| Client keys are unique identifiers that allow clients to sign Open Payments requests and verify their identity. |
There was a problem hiding this comment.
Who is "their"? Clients or requests?
There was a problem hiding this comment.
Good catch...I'll add "the client's identity".
| .DS_Store | ||
|
|
||
| # Claude Code | ||
| .claude |
There was a problem hiding this comment.
Was this a Prettier addition?
There was a problem hiding this comment.
I installed claude code locally for some experimentation, and I'm pretty sure it was an artifact from that. I pulled that back out, so it shouldn't show up anywhere else.
I waffled a bit on whether to include it or not. I feel like the rest of the glossary terms are foundational to Open Payments. Things like ASE and infrastructure pieces like auth server, etc. Directed identity feels like a layer deeper than those. However, because it's a "thing with a name" now across multiple pages it's worth including? I could go either way. |
Enhanced some wording and fixed gitignore
Fixes #DOC-34
Updated the following pages to document directed identity:
Also, bumps the
open-payments-specificationssubmodule to pick up the latest spec changes, including directed identityChecklist
docs:fixes #pnpm formatandpnpm lint