-
Notifications
You must be signed in to change notification settings - Fork 16
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
VDR: SubjectManager returns DIDs in preferred order #3291
Conversation
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.
The ordering is controlled by a config flag, and it impacts the order of results presented to the user. Should this be in config description or do we not want to make such guarantees
Co-authored-by: Gerard Snaauw <33763579+gerardsn@users.noreply.github.com>
CLI passing is (also) documented in https://nuts-node.readthedocs.io/en/latest/pages/deployment/configuration.html |
last comment is in the wrong PR? |
Oops, comment moved to #3290 |
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.
This will probably also impact which DID is used to sign a VP? If so change docs for config accordingly.
around line 660 of |
I don't think this should matter any more, since any use of DIDs is bound by what the other side accepts. So there's not really a place for "preferred order". Although weird, if a verifier accepts 2 DID methods and the holder has both, it doesn't matter if it presents the first DID initially, and the second DID at some later point? |
@woutslakhorst would you like to re-review? |
No description provided.