So we have this shared vaults wherein two members are able to access one vault with many accounts within that vault, that's usually how it works right? The weird thing is that I'm able to go through using the same login credentials as well as the verification code. As for the other member, he logged in using the same credentials as I did and he's able to go through email address and password but not the verification code because it says it's "Incorrect". These are following troubleshooting steps we did:
I'm currently asking the community as to why this happens in case some of you have an answer for that. That would be a really big help!
Hello @Nimbl Servicing Confluence
The biggest thing to address here is the access model itself. Sharing credentials between two people is a massive security risk and actually goes against Atlassian’s customer agreement.
Atlassian Customer Agreement | Atlassian
emergency recovery keys are single-use. Once you use one, it's dead, and a brand-new key is generated to replace it. If a new one was spun up, the old one won't work anymore.
If they still can't get in after setting up their own account and verification, you'll need to reach out to Atlassian Support. We can't see the backend authentication states here in the Community, so they'll need to look under the hood. (And if the "shared vault" you mentioned belongs to an external password manager, you'll want to check with that specific vendor, since Bitbucket doesn't control those vault permissions).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.