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

Multisig OOBI is missing end role authorization messages after member joins #305

Open
lenkan opened this issue Oct 11, 2024 · 1 comment

Comments

@lenkan
Copy link
Contributor

lenkan commented Oct 11, 2024

There is a bug when a group is created with a signing threshold that is less than 100%. For example, consider a group with 3 members and a signing threshold of 2.

Affected versions

  • main as of 2024-10-11
  • 0.2.0-dev3
  • Probably before as well

Steps to reproduce

  1. Member 1 and 2 creates group consisting of member 1, 2, and 3
  2. Member 1 and 2 authorizes the end role for the agent of member 1
  3. Generate OOBI and verify that the oobi contains the /end/role/add message
  4. Member 3 creates the group
  5. Generate OOBI and verify that the oobi contains the /end/role/add message

Expected result

The /end/role/add message can be found in the oobi response in both step 3 and 5

Actual result

The /end/role/add message is missing from the oobi in step 5.

Notes

A reproduction is available here: https://github.com/nordlei/vlei-sandbox/blob/main/src/issues/multisig-join-late-no-endroles.test.ts

This happens because all three group members are using the same KERIA instance and currently, when KERIA responds to an OOBI request, it reads this information from the last agent that joined the group. In this case, that agent does not yet have the end role information.

@lenkan
Copy link
Contributor Author

lenkan commented Oct 11, 2024

This is where the agent is loaded for the oobi request:

agent = self.agency.lookup(pre=aid)

It will return the agent that was the last one to call "incept" on the agency for the group. I was able to resolve this issue by requiring the eid parameter on the OOBI endpoint and use that to retrieve the agent instead. In other words, KERIA would require you to specify which agent to load the OOBI from.

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

1 participant