https://github.com/w3c/vc-data-integrity/pull/148/files
Raising this PR here, in case you have time to comment.
We expect something similar to happen for COSE Keys in the future, so
including both lists.
For background:
The W3C has a structure called a "VerificationMethod" which can express
relationships between identifiers (such as DIDs) and public keys (in any
representation, not just JWK).
In the case of JWK public Keys, the json member "publicKeyJwk" is used.
This PR defines the other side of this member, in cases where the private
key is exportable.
Here is a complete example:
{
"id": "did:example:123#key-456",
"type": "JsonWebKey",
"controller": "did:example:123",
"publicKeyJwk": {
"kty": "OKP",
"crv": "Ed25519",
"x": "ENqgw6Hv-5M0igPQGtx7iA6BZkrKJ8VI4Mw2d4Be9D8"
},
"privateKeyJwk": {
"kty": "OKP",
"crv": "Ed25519",
"x": "ENqgw6Hv-5M0igPQGtx7iA6BZkrKJ8VI4Mw2d4Be9D8",
"d": "Mwn-HlkrBlVBOl1QlfQgG5BmucOEIj12IItidki54q8"
}
Previously "privateKeyJwk" was used in some implementations.
After this PR is merged, implementations will be expected to use
"secretKeyJwk" instead, concrete example:
{
"id": "did:example:123#key-456",
"type": "JsonWebKey",
"controller": "did:example:123",
"publicKeyJwk": {
"kty": "OKP",
"crv": "Ed25519",
"x": "ENqgw6Hv-5M0igPQGtx7iA6BZkrKJ8VI4Mw2d4Be9D8"
},
"secretKeyJwk": {
"kty": "OKP",
"crv": "Ed25519",
"x": "ENqgw6Hv-5M0igPQGtx7iA6BZkrKJ8VI4Mw2d4Be9D8",
"d": "Mwn-HlkrBlVBOl1QlfQgG5BmucOEIj12IItidki54q8"
}
Regards,
OS
--
ORIE STEELE
Chief Technology Officer
www.transmute.industries
<https://transmute.industries>
_______________________________________________
jose mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/jose
