Possible bug with shared vaults

[pragmaticpandy]

I've created an account and set up Sync with a vault with e2e encryption off.
Then i shared this vault with a different account

that account is trying to sync headless

ob login works
ob sync-list-remote works:

Fetching vaults...

Vaults:

Shared vaults:
  ffffff  "the-vault-that-was-shared"  (North America)

but then when that account does
ob sync-setup --vault "$OBSIDIAN_VAULT_ID" --path "$VAULT_DIR"
the result is exit code 2:

Fetching vault info...
Setting up...
Failed to validate password.

but we know the password is correct because login and other commands that require auth (sync-list-remote) worked
the headless box is debian—Linux 6.12.12+bpo-cloud-amd64 (x64)

---

Edit, I tried with an encrypted vault. again login is fine and the vault appears when logged into the account the vault was shared with.

ob sync-setup --vault $OBSIDIAN_ENCRYPTED_VAULT_NAME --path /data/workspace --password $OBSIDIAN_VAULT_ENCRYPTION_KEY

has output:

Fetching vault info...
Setting up...
Failed to validate password.

[lishid]

That's strange. The only two ways to get this error is if 1) the password wasn't provided, or the provided password did not validate successfully with the server. This isn't your account password, but the password provided for E2EE. Given you said you tried with an E2EE vault, I'm assuming your first try was with a managed password vault.

In that case, there's two things that could have gone wrong. 1) Somehow there's an encoding difference which is causing the keyhash to be verified incorrectly, or 2) somehow the network connection to the server is failing.

I will issue an update to show the exact error from the password verification network call, but it is possible that your Sync subscription has expired or something of the sort is causing the vault verification to fail.

[pragmaticpandy]

Given you said you tried with an E2EE vault, I'm assuming your first try was with a managed password vault.
correct

Does the receiving account also need to pay for obsidian sync? Because this one was not paying, so maybe that is the issue. I had assumed only the owning account needed to pay but maybe that assumption is wrong

btw I got around this by using the same account, and achieved effective account isolation by adding e2e encryption passwords to all vaults. then the headless box only has the encryption password for one

[lishid]

That's right. If that is the case, I will double check and make sure the error message is properly surfaced in the next update.