Released docs. You are viewing the documentation published with v0.46.0. Development docs are available at Latest.
Publish the active and retained public verification keys
const url = 'https://example.com/.well-known/evidence/jwks.json';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://example.com/.well-known/evidence/jwks.jsonParameters
Section titled “Parameters”Header Parameters
Section titled “Header Parameters”The exact strong entity tag from a prior response.
Responses
Section titled “Responses”Evidence public verification keys
object
object
Example
{ "keys": [ { "alg": "ES256", "crv": "P-256", "kty": "EC" } ]}Headers
Section titled “Headers”Public metadata may be cached for at most ten minutes.
Strong SHA-256 entity tag over the exact response bytes.
Effective W3C trace context. One valid inbound traceparent is retained; missing, invalid, or duplicate values are replaced and tracestate is never reflected.
The public key set is unchanged
Headers
Section titled “Headers”Public metadata may be cached for at most ten minutes.
Strong SHA-256 entity tag over the exact response bytes.
Effective W3C trace context. One valid inbound traceparent is retained; missing, invalid, or duplicate values are replaced and tracestate is never reflected.
Cookies on Registry Stack
We use optional cookies to understand how you use the main Registry Stack website and this documentation. If you contact us, we may link this activity to your enquiry. You can change your choice at any time. Read the privacy policy.
Your browser asks sites not to track you, so optional tracking stays off.
We could not use or save that choice. Optional tracking remains off.