-
Notifications
You must be signed in to change notification settings - Fork 42
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
Issues with 'did:key' compatibilty #79
Comments
Unfortunately, I’m not sure of the state of did:key usage. What mediator are you using? Definitely using did:key in a DIDComm message for routing should be possible. We’ll look at where this is in the backlog and see if we can push it up. |
I am also facing some issues using the code here as a mediator. The issue may be related to did:key The attached PDF contains a log of the messages exchanged (on mobile agent - aries-framework-kotlin): Also, on the ACA-Py side. When using this mediator:
When using the Indicio public mediator:
As a further observation, when using the Indicio public mediator, the DID Doc is:
Importing pydid and deserialising the above results in:
Note that the service is With this mediator, it results in unknown service. Here is the doc:
And here is the result from
Both the mediator and the cloud agent are running aca-py |
I'm looking into this. This has some ties to work I've already started in openwallet-foundation/acapy#2516 |
I successfully run the mediator and connect it to iOS agent.
Then I connect iOS agent with ACA-py Faber agent. Once the agents are connected and I send some DIDComm message from Faber to iOS, I run into an error that is caused because
routingKeys
is usingdid:key
prefix that Faber doesn't know how to parse.Here is the error:
My question: Is there a way to set this mediator to user 'raw keys' for routingKeys parameter?
Or on the other hand - how should I upgrade Faber agent to support
did:key
prefix?The text was updated successfully, but these errors were encountered: