A stored URL for a Bitwarden secret requires re-authentication

Hi everyone,

I’m new here, so please be gentle with me! :blush:

I use a password manager other than Bitwarden for storing my passwords, but I keep the 2FA TOTP codes for those entries in Bitwarden. Each entry in my primary password manager has a corresponding entry in Bitwarden containing the TOTP code. This setup is a bit of a hassle, but it provides an extra layer of security. If my primary vault is compromised, the attacker would also need access to Bitwarden to get the 2FA codes.

To simplify things, I want to add a URL within each entry in my primary password manager that links to the corresponding TOTP entry in Bitwarden’s web interface. This way, I can easily click the link to bring up the code. Let’s assume I’m already logged into Bitwarden on my primary browser.

The problem I’m facing is that even though I’m logged into Bitwarden’s web interface on my default browser, I’m prompted to log in again before it displays the entry. Is there a way to eliminate this extra login step?

For the record, my browser is Microsoft Edge on Windows 11.

Any ideas or suggestions would be greatly appreciated!

@DSeawel It seems that the issue is that the Web Vault login is only valid within the same tab where you logged in. Unless you open the deep link (to the desired vault item) in the same tab where you logged in, you will need to authenticate.

A work-around would be to use links to the browser extension UI instead (after logging in to the extension). For example, if you are using the Chrome browser extension, instead of linking to

https://vault.bitwarden.com/#/vault?cipherId=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

you can try linking to the following:

chrome-extension://nngceckbapebfimnlniiiahkandclblb/popup/index.html#/view-cipher?cipherId=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

 

For me, the following link format works in Edge (assuming that the browser extension is already unlocked):

extension://jbkfoedolllekgbhcbcoahefnbanhhlh/popup/index.html#/view-cipher?cipherId=xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
1 Like

Another possibility is a single vault with peppered passwords+TOTP. Peppering is a middle ground, offering some of the advantages of two vaults, but with only a small increase in user/admin hassle.

Your call if it is right for you.

I like this.
It works if I paste the string with the cipherId into a new tab in the browser.
But I’m a little stumped about how I might be able to turn this into a clickable hyperlink in the original password manager that will open Chrome or Edge to the page showing the Bitwarden entry.

Do you have any ideas to overcome this piece?

I can sort of get it to work in Chrome, but not Edge, unfortunately. In Chrome, if you open the link in a new tab (e.g., using target="_blank"), then the correct URL is transferred to the address bar (but not loaded). Thus, you would need to click the link, focus the address bar, and then hit Enter. However, as I said, this approach does not work in Edge.

In the end, I think that @DenBesten is on the right track — you should rethink your approach. Personally, I think that the best solution for your use-case is simply to add URL strings to each TOTP entry stored in your Bitwarden password manager. Then, Bitwarden will automatically find the correct TOTP entry using its URI matching functionality. You will then be able to easily copy or auto-fill the TOTP code using the browser extension pop-up window, or using the right-click context menu, or using keyboard shortcuts.

Thanks for the suggestions!

1 Like