-
Notifications
You must be signed in to change notification settings - Fork 233
refactor(anoncreds): master secret to link secret #1415
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
refactor(anoncreds): master secret to link secret #1415
Conversation
Signed-off-by: Ariel Gentile <gentilester@gmail.com>
Yeah the credential definition should still use |
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.
Fabulous!
masterSecret?.handle.clear() | ||
return { | ||
linkSecretId: options?.linkSecretId ?? utils.uuid(), | ||
linkSecretValue: LinkSecret.create(), |
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.
much better :)
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.
Yeah I was a really happy moment for me when I did that update :-D
@genaris https://github.com/hyperledger/anoncreds-rs/releases/tag/v0.1.0-dev.13 is cooking, after which we can merge this PR I think? |
Yes, I think we'll need to update some package.json files first so yarn.lock takes this new version. |
Signed-off-by: Ariel Gentile <gentilester@gmail.com>
Updates
AnonCredsRsHolderService
according to the recent changes in@hyperledger/anoncreds
API and applies transformations to credential request metadata (including migration script).There is a test that is not passing, because anoncreds-rs expects the credential definition to have a
link_secret
field instead of the former/legacymaster_secret
field (this is according to this test added recently by @blu3beri).From my understanding, we should still be tied to
master_secret
in this case but AnonCreds spec is not consistent about this: in section 7.2.2., it first shows an example where link_secret is used (supposed to be based in an example in Sovrin MainNet which actually uses master_secret). And then, when describing all the fields within a Credential Definition, it states: