Open lenkan opened 6 months ago
From our dev meeting: Only one oobi is being chosen in the signify-ts example. There are a number of options:
Here is a reference to a discussion in discord regarding this: https://discord.com/channels/1148629222647148624/1148734044545228831/1194270946215854182
There has been some discussion on github and discord regarding how multisig OOBI urls work. This issue on signify-ts contains some further references: https://github.com/WebOfTrust/signify-ts/issues/193
Consider a group AID
multisig
with participantsmember1
andmember2
and their keria agentsagent1
andagent2
. Currently, when callingGET /oobis/multisig
to generate an OOBI url for the group, you have to specify the role as eitheragent
,witness
orcontroller
.So, for example, if
member1
would call this endpoint to generate an OOBI url for the group they would specify the role parameteragent
and and get a result:If another AID, for example a credential issuer resolves this OOBI url and then grants a credential to that AID, only
member1
would receive this message.The current workaround is to construct an URL on the client side by stripping the
/agent/<agent1 aid>
part of the URL. So you would get:See the example scripts in signifypy and signify-ts: