Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kid restrictions for JSON headers and new kyu #150

Open
dwaite opened this issue Nov 12, 2024 · 1 comment
Open

kid restrictions for JSON headers and new kyu #150

dwaite opened this issue Nov 12, 2024 · 1 comment

Comments

@dwaite
Copy link
Collaborator

dwaite commented Nov 12, 2024

The definition of kid is binary in CBOR and string in JSON, with no mapping between the two defined.

I propose JWP kid is restricted to be a binary value represented in BASE64URI encoding. This will limit the ability give keys friendly names or names which correspond to some other system, e.g. GUIDs.

I also propose a new header parameter, kyu, for key URL, to represent keys which are not identified by identifying labels but by location. An example of kid in JWS being used this way would be DIDs.

@selfissued
Copy link
Collaborator

I don't see a practical reason to be able to map Key ID values between JWPs and CWPs. They will be different ecosystems.

In one case, I suggest that we recommend the use of JWK Thumbprint values as "kid" values. In the other, I suggest that we recommend the use of COSE_Key Thumbprint values as "kid" values.

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

No branches or pull requests

2 participants