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

An idea for the endorsement of a badgeclass #16

Open
wants to merge 14 commits into
base: master
Choose a base branch
from

Conversation

ottonomy
Copy link

A possible extension to allow external organizations to endorse an issuer's badgeClass by providing a badgeClass extension with a JSON Web Signatures-signed block. This is an extension to allow issuers to solicit endorsements, which wouldn't work for endorsers to add their endorsement without the issuer's permission. I'm not absolutely sure just what should constitute the payload of the signature. This example suggests signers embed what they know of the badgeClass in the signature extension, copying the existing properties from above. It's not perfect.

If signers know the URL of the badgeClass-to-be-endorsed, they could include that, but that wouldn't be enough to protect against the badgeClass being edited to become something that the signer didn't want to endorse.

Potential downside: The only way to revoke this kind of signature without cooperation of the issuer would be to pull the public key.

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

Successfully merging this pull request may close these issues.

1 participant