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.

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

How to maintain multiple web socket session opposite of a single connection id in aca-py mediator for multi-Device Message Delivery #3196

Open
Arif-Shahriar028 opened this issue Aug 25, 2024 · 1 comment

Comments

@Arif-Shahriar028
Copy link

Arif-Shahriar028 commented Aug 25, 2024

Using wallet backup and restore concept (in bifold wallet), I am using same wallet with same data in two mobile devices. In my expectation, if any agent sends a message to my wallet agent, then both of the device should get the messege (via acapy mediator). But only one device is receiving the message because of mediator's websocket session management.

So in aca-py mediator, for a connection id, I want to maintain multiple websocket session so that if any agent send message to my mobile wallet, both mobile should receive the message.

I have read a documentation in hackmd about the architecture of this session handling process, but there is not much information for clear understanding.

How can I maintain a list of sessions associated with each connection ID where each session corresponds to a different device?

I have added a simple illustration of my thought:

image

@swcurran
Copy link
Contributor

swcurran commented Sep 4, 2024

Unfortunately, this type of functionality is not currently supported. Private keys needed to decrypt messages sent to an instance of a wallet are not shared across wallets, and as a result, messages are specific to a device. Further, there is not in the current mediator protocols a method for forwarding a single message to more than one wallet instance.

These types of issues do need a solution, but to this point have not been a priority. This is something you might want to bring up at the DIDComm Working Group at the Decentralized Identity Foundation (https://decentralized.identity).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants