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.

Sign up for GitHub

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

Jump to bottom

Verify Authenticity of the Issuer reference in a badge #78

Closed
timothyfcook opened this issue Sep 7, 2016 · 2 comments
Closed

Verify Authenticity of the Issuer reference in a badge #78

timothyfcook opened this issue Sep 7, 2016 · 2 comments
Milestone
2.0 Release Candi...

Comments

@timothyfcook
Copy link
Contributor

timothyfcook commented Sep 7, 2016 •
edited
Loading

User Stories

  • As a badge consumer, I want to verify that the badge was awarded by the expected issuer Profile, so that I can ensure its authenticity.
    • Note: this does not verify that the identity of the issuer Profile is authentic, but completes the first step to verify that the issuer profile referenced in the BadgeClass and/or Assertion was truly the creator of the BadgeClass.
  • As a badge consumer, I want to verify that the badge was awarded to the expected recipient Profile, so that I can ensure its authenticity.
@timothyfcook timothyfcook changed the title Verify Authenticity of the Issuer's Profile Verify Authenticity of the Issuer reference in a badge Sep 7, 2016
@ottonomy ottonomy modified the milestone: 2.0 Prototypes Sep 7, 2016
@1l2p
Copy link

1l2p commented Oct 1, 2016

This seems easier to implement through the use of a blockchain or other ledger that maintains a list of badge issuing transactions. Identity can be represented by a set of public addresses, controlled by the issuer and the recipient respectively.

@ottonomy ottonomy mentioned this issue Dec 31, 2016
Merged
@mgylling
Copy link
Contributor

mgylling commented Feb 1, 2017

Closing this issue, as it was resolved by the 2.0 Recommendation. This issue and all other issues resolved by 2.0 can be found via the 2.0 Release Candidate milestone and PR #99.

@mgylling mgylling closed this as completed Feb 1, 2017
amiller-ims pushed a commit that referenced this issue Dec 11, 2020
@ahripak
Merge pull request #78 from justinpitcher/domain-statement
646c3b3 
Approving based on no feedback since last workgroup meeting.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
2.0 Release Candidate
Development

No branches or pull requests
4 participants
@1l2p @mgylling @timothyfcook @ottonomy