Publish JWT VC Issuer Metadata for the SD-JWT VC response format
const url = 'https://example.com/.well-known/jwt-vc-issuer';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/jwt-vc-issuerDiscovery is not a trust anchor. The document republishes the same public keys under the provider identity the assertion names, and resolution is meaningful only when that identity is the HTTPS origin of the deployment.
Parameters
Section titled “ Parameters ”Header Parameters
Section titled “Header Parameters”The exact strong entity tag from a prior response.
Responses
Section titled “ Responses ”Provider identity and public verification keys
object
Examplegenerated
{ "issuer": "example", "jwks_uri": "https://example.com"}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 issuer metadata 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.