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

Overlapping Jitsi sessions when two ceremonies are started very close to each other #2

Open
nkongsuwan opened this issue Jul 29, 2024 · 7 comments

Comments

@nkongsuwan
Copy link
Collaborator

nkongsuwan commented Jul 29, 2024

Describe the bug

This is probably a corner case that might be difficult to reproduce. I encountered overlapping ceremonies, where a member of the previous ceremony got stuck in the Jitsi session and appeared in the next ceremony.

In summary, I started two workflows in parallel, one for issuance of an ECR and another for an OOR. I completed the ECR issuance ceremony and then immediately started the OOR issuance ceremony.

Note 1: This may or may not be relevant. For some reason, the ECR person who got stuck in the Jitsi session never received the issued ECR credential. The QVI AID successfully issued the ECR credential, and the LE AID also successfully issued the ECR Auth credential.

Note 2: I did not click "View Credential" at the end of the ceremony for the ECR person.

My guess is that I terminated the ceremony before the ECR person finished admitting the credential. Since the admit was not finished when the ceremony was terminated, the ECR person got stuck in the Jitsi session.

To Reproduce

These are the steps I took:

  1. Start an ECR issuance workflow and complete ID verification
  2. Start an OOR issuance workflow and complete ID verification
  3. Start and complete the ECR issuance ceremony. Here, the ECR person DOES NOT click "View Credential" at the end of the ceremony, and one of the QARs terminates the ceremony.
  4. Start the OOR issuance ceremony right after the previous ceremony was terminated.

Expected behavior

Different issuance workflows should create non-overlapping Jitsi sessions.

Screenshots

Here is the screenshot at the beginning of the OOR issuance ceremony. The screen displayed "Successful Issuance!" even before all participants had joined. Notice that the "TEST-ECR" as well as LAR3 from the previous session appeared on the QAR1's screen (the left side). For some reason, the "TEST-ECR" and LAR3 do not appear on the QAR2's screen (the right side).
Screenshot 2567-07-14 at 21 41 21

Desktop (please complete the following information):

  • OS: MacOS Sonoma 14.5
  • Browser: Chrome
  • Version: 126.0.6478.183 (Official Build) (arm64)

Additional context

I encountered the error in the development environment of Origin Asia https://dev.asia.origincloud.net/.

@nkongsuwan nkongsuwan changed the title Overlapping Jitsi sessions when a new ceremony is started right after Overlapping Jitsi sessions when two ceremonies are started very close to each other Jul 29, 2024
@dhh1128
Copy link
Member

dhh1128 commented Jul 30, 2024

The identifier for this bug in our internal system is DF-2231. We are tracking it and will report back.

@dhh1128
Copy link
Member

dhh1128 commented Aug 7, 2024

Hi, I'm just noting that this bug was reassigned in our system from Yeasin to @Arsh-Sandhu .

@rc-provenant
Copy link

@nkongsuwan were you issuing the ECR and OOR to two different people or to the same person? Did you use different phone numbers when specifying phone numbers for IDVerse?
Btw, the screenshot is no longer available. Do you have a copy?

@nkongsuwan
Copy link
Collaborator Author

@rc-provenant I believe I issued ECR and OOR to two different people/wallets.

I used Mock ID Verification for both. I don't remember the phone numbers as I typed random numbers. I could have accidentally types the same numbers for both.

I put the screenshot here.
https://finemaco-my.sharepoint.com/:i:/g/personal/win_finema_co/EfUTxscYrWRPm2ljZJqRfFoBHd_akcMLaDDF_aNt7cRMkw?e=05pltN

@dhh1128
Copy link
Member

dhh1128 commented Aug 15, 2024

[from twin in jira]
At 2024-08-15T00:39Z, Daniel Hardman said: we have not yet had time to experiment with this.

@dhh1128
Copy link
Member

dhh1128 commented Aug 21, 2024

[from twin in jira]
The issue is assigned in jira to Arshdeep Singh.

@dhh1128
Copy link
Member

dhh1128 commented Aug 28, 2024

[from twin in jira]
The issue is assigned in jira to Yeasin Hossain.

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

3 participants