-
Notifications
You must be signed in to change notification settings - Fork 1
feat(rust/signed-doc): Use Catalyst ID as KID #194
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
Conversation
* verify signatures with public (verification) key * todo: verify UUIDs
* verify doc type, id and ver
* verify extra fields
|
✅ Test Report | |
|
✅ Test Report | |
|
✅ Test Report | |
|
✅ Test Report | |
|
✅ Test Report | |
The base branch was changed.
|
✅ Test Report | |
Mr-Leshiy
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
✅ Test Report | |
Description
Use the catalyst-id and type for it in catalyst-libs, to parse and validate kid for signatures on a signed document.
Implement an authors() function on the document type, which returns a list of all authors (being short_id() versions of all kids. Implement an kids()function on the document type which returns a list of allkids()needed to validate the document. Expose a validate function which takes an algorithm identifier and public key which matches the algorithm, for eachkidreturned by thekids()` function. There is no need to partially validate, so if all public keys are not supplied then validation has failed.
The caller will extract the public key and algorithm from the RBAC registration.
Do not create a new set of types for these, use common types supported and exposed by the RBAC registration crate itself.
Related Issue(s)
Closes #161
Please confirm the following checks