Google Workspace SCIM bridge not syncing group members when email address case differs

I just deployed 1Password SCIM bridge v2.6.0 for Google Workspace on GCP (thanks for releasing that!)

One weird scenario I'm hitting is that for an as-yet-unknown reason[1], some of our 1Password users email addresses begin with a capital letter, when their corresponding Google account email addresses do not (e.g. John@example.com in 1Password, john@example.com in Google Workspace). Because of that difference, while john@example.com and jane@example.com are both members of the group foo-group@example.com which is now syncing to 1P via 1P SCIM bridge, Jane appears in the corresponding 1Password group, but John does not.

As best I can tell, this is because John got added to 1Password as with an uppercase first character in his email address (John@example.com) rather than lowercase john@example.com.

What's the best path for resolving this conflict? I'd ultimately like to make sure the emails in 1Password match the case of the emails in Google, but I don't see a straightforward way of correcting the user email address in 1Password.

[1] This case issue is probably happening further up the provisioning chain as we have a payroll system connected to Google Workspace that provisions new Google accounts for new employees, and is probably upper-casing the email address.

---

1Password Version: 8.9.4
Extension Version: 2.3.7
OS Version: macOS 12.6
Browser:_ Chrome