By using the did-manager crate, it is possible to produce and resolve DID documents for a variety of DID methods. With dev mode enabled, a new settings entry appears that offers easy introspection of currently supported methods as well as basic management (such as selecting the preferred method to be used). Additionally, the DID of the Connection is displayed (only in dev mode) that was used in the latest interaction.
Also, some smaller refactorings are part of this PR:
rename default_did_method to preferred_did_method (more suitable)
remove primary_did from Profile (unused)
Links to any relevant issues
90
93
94
Depends on
197
How the change has been tested
Build for a physical iOS device, interaction with UniCore
Definition of Done checklist
Add an x to the boxes that are relevant to your changes.
[x] I have followed the contribution guidelines for this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
Description of change
By using the
did-managercrate, it is possible to produce and resolve DID documents for a variety of DID methods. With dev mode enabled, a new settings entry appears that offers easy introspection of currently supported methods as well as basic management (such as selecting the preferred method to be used). Additionally, the DID of the Connection is displayed (only in dev mode) that was used in the latest interaction.Also, some smaller refactorings are part of this PR:
default_did_methodtopreferred_did_method(more suitable)primary_didfromProfile(unused)Links to any relevant issues
90
93
94
Depends on
197
How the change has been tested
Build for a physical iOS device, interaction with UniCore
Definition of Done checklist
Add an
xto the boxes that are relevant to your changes.