You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There has been some discussion on github and discord regarding how multisig OOBI urls work. This issue on signify-ts contains some further references: WebOfTrust/signify-ts#193
Consider a group AID multisig with participants member1 and member2 and their keria agents agent1 and agent2. Currently, when calling GET /oobis/multisig to generate an OOBI url for the group, you have to specify the role as either agent, witness or controller.
So, for example, if member1 would call this endpoint to generate an OOBI url for the group they would specify the role parameter agent 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:
https://keria-url/oobi/<multisig aid>
See the example scripts in signifypy and signify-ts:
From our dev meeting:
Only one oobi is being chosen in the signify-ts example. There are a number of options:
Clients can review the agent OOBIs and return the non-role OOBI (like seen in the tests). Does this belong in the logic or API? If this is handled at the API level it would help the user to receive the generic OOBI. @Arsh-Sandhu will send his fix.
There has been some discussion on github and discord regarding how multisig OOBI urls work. This issue on signify-ts contains some further references: WebOfTrust/signify-ts#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:
The text was updated successfully, but these errors were encountered: