Skip to content

Document 51Did creator context verification - #221

Open
jwrosewell wants to merge 3 commits into
mainfrom
doc/51did-context-verification
Open

Document 51Did creator context verification#221
jwrosewell wants to merge 3 commits into
mainfrom
doc/51did-context-verification

Conversation

@jwrosewell

@jwrosewell jwrosewell commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

Documents creator context verification (context for short) alongside the existing signature verification in the 51Did identifier docs.

What

  • New Verifying the device context subsection under Validation: what the check confirms (the 51Did is being verified on the same device it was created on), that it is metered and evaluated only within the 51Degrees service, and the must-call-from-the-browser rule (a server-side call reports invalid).
  • The three verify endpoints and their JSON: signature-only /verify, context-only /verify-context, and combined /verify-full. All three require a Resource Key and are metered (401 without a key, 403 without the entitlement).
  • The context result values (verified / invalid / absent / indeterminate) and the combined signature+context states, including that a verified context cannot be forged by tampering.
  • A diagnostic factors block (transport / device / network), returned when the context does not cleanly verify, to help locate an integration problem. Neutral labels only.
  • The render-time (bid-to-render) use case and the fetch-cross-origin integration note.

Outcome-level only: describes what is checked and what each result means, not how it works. The published payload layout table is unchanged.

…tates

Describe context verification alongside signature verification: what it
confirms (same device the identifier was created on), the three verify
endpoints and their JSON, the context result values, the combined
signature/context states, the must-call-from-the-browser rule, and the
render-time use case. Outcome-level only.
@github-actions

Copy link
Copy Markdown
Contributor

Documentation preview 👀

Add the verify-context and verify-full response shapes, the resource-key and
metering requirement, and the diagnostic factor block. Clarify that a verified
context cannot be forged by tampering.
@jwrosewell
jwrosewell marked this pull request as ready for review July 18, 2026 17:12
Name the check "creator context" verification (context for short) in the identifier docs so it is clear what the context is. Endpoint and field names are unchanged.
@jwrosewell jwrosewell changed the title Document 51Did context (device) verification Document 51Did creator context verification Jul 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant