"Unable to retrieve Bitwarden Credentials"

Hello Bill,

Thank you for contacting us on that matter!

A ticket has already been opened with our Engineering Department to see what could be causing this.
They would require more details if you could answer the following :

1- When was the Bitwarden account created? Is it a new account, or a very old one?

2- Is there any particularity to the Bitwarden organization the account is a part of? For example, is the organization disabled, or has there been a deleted organization that the account used to have access to, etc?

3-Has there been any account encryption key rotation performed by the account? For more information:  https://bitwarden.com/help/article/account-encryption-key/ 
4- Has any other special action been performed on the vault or on the organization that differs from a “default” configuration?

5- Anything that comes to mind might be helpful to diagnose this issue. We haven’t been able to reproduce it with our multiple accounts, both new and old ones, with the same kind of authentication configuration as you are using.

Best Regards,

Thank you James.

In order;

1. Bitwarden account was created many months ago. It isn't new. On a side note I've noticed a lot of Bitwarden application updates (desktop app, Android phone app)
2. Nothing unusual about the Organization. It is a paid account, mostly for family. The passwords are not shared and it has been working fine for a while now (though there were issues inside one environment I expect that was proxy server/security system related).
3. No account key rotation. I've removed and recreated the Bitwarden credentials under the Accounts setting.
4. No special actions from default configuration. I like defaults because I don't have to remember to set things up differently.
5. I have noticed some erratic behavior, there is an option to 'remember device' in the DUO two factor configuration and it has popped up a few times after I told it to remember. Doesn't happen often but does make me think things were being changed 'behind the scenes'

Is there a way to delete the local Bitwarden configuration cache integration? A file or a registry key? I have the problem occuring on three different systems (All Windows 10).

I am having the identical problem. It started some time before Yesterday (5/18). I am using the Bitwarden Personal "Free account". I have had the account well over a year and had no issues with it. I did update Remote Desktop Manager to the latest release today and it is still an issue.

• Bitwarden account created more than a year ago.
• Changed my Default Bitwarden Password
• I did NOT do an account key rotation.
• I've removed and recreated the Bitwarden credentials under the Accounts setting.
• No special actions from default configuration.

Randy

Hello,

Thank you for your replies, this information has been provided to our Engineering Department and we will get back to you as soon as we will have an update on that matter.

Best regards,

I'm getting this as well (Just started in the past 2 days). 2021.1.26.0 64-bit

* My bitwarden account is over a year old
* No recent org changes, current org is active
* No recent rotations
* No special changes
* Absolutely nothing has changed on my account from when this was working 2 days ago to now.

This is the error in the application log:

PasswordManagerAccess.Common.InternalErrorException: Network request or response parsing failed ---> Newtonsoft.Json.JsonReaderException: Unexpected character encountered while parsing value: e. Path '', line 0, position 0.
at Newtonsoft.Json.JsonTextReader.ParseValue()
at Newtonsoft.Json.JsonReader.ReadForType(JsonContract contract, Boolean hasConverter)
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(JsonReader reader, Type objectType, Boolean checkAdditionalContent)
at Newtonsoft.Json.JsonSerializer.DeserializeInternal(JsonReader reader, Type objectType)
at Newtonsoft.Json.JsonConvert.DeserializeObject(String value, Type type, JsonSerializerSettings settings)
at Newtonsoft.Json.JsonConvert.DeserializeObject[T](String value, JsonSerializerSettings settings)
at PasswordManagerAccess.Common.RestClient.MakeRequest[TContent,TData](String endpoint, HttpMethod method, HttpContent content, Dictionary`2 headers, Dictionary`2 cookies, Int32 maxRedirects, Func`2 deserialize)
--- End of inner exception stack trace ---
at PasswordManagerAccess.Bitwarden.Client.RequestAuthToken(String username, Byte[] passwordHash, String deviceId, SecondFactorOptions secondFactorOptions, RestClient rest)
at PasswordManagerAccess.Bitwarden.Client.Login(String username, Byte[] passwordHash, String deviceId, IUi ui, ISecureStorage storage, RestClient rest)
at PasswordManagerAccess.Bitwarden.Client.OpenVault(String username, String password, String deviceId, String baseUrl, IUi ui, ISecureStorage storage, IRestTransport transport)
at PasswordManagerAccess.Bitwarden.Vault.Open(String username, String password, String deviceId, String baseUrl, IUi ui, ISecureStorage storage)
at Devolutions.RemoteDesktopManager.Managers.BitwardenManager.c2b5cd6838c9b19c2e1e62f246f08131c.c5dd20686dcb6fc762f9a873101f19386()

Me too - same error in Application log as rdm8 - except my version is 2021.1.29.0 64-bit

Me too - same error in Application log - my RDM version is ENTERPRISE EDITION 2021.1.30.0 64-bit

PasswordManagerAccess.Common.InternalErrorException: Network request or response parsing failed ---> Newtonsoft.Json.JsonReaderException: Unexpected character encountered while parsing value: e. Path '', line 0, position 0.
at Newtonsoft.Json.JsonTextReader.ParseValue()
at Newtonsoft.Json.JsonReader.ReadForType(JsonContract contract, Boolean hasConverter)
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(JsonReader reader, Type objectType, Boolean checkAdditionalContent)
at Newtonsoft.Json.JsonSerializer.DeserializeInternal(JsonReader reader, Type objectType)
at Newtonsoft.Json.JsonConvert.DeserializeObject(String value, Type type, JsonSerializerSettings settings)
at Newtonsoft.Json.JsonConvert.DeserializeObject[T](String value, JsonSerializerSettings settings)
at PasswordManagerAccess.Common.RestClient.MakeRequest[TContent,TData](String endpoint, HttpMethod method, HttpContent content, Dictionary`2 headers, Dictionary`2 cookies, Int32 maxRedirects, Func`2 deserialize)
--- End of inner exception stack trace ---
at PasswordManagerAccess.Bitwarden.Client.RequestAuthToken(String username, Byte[] passwordHash, String deviceId, SecondFactorOptions secondFactorOptions, RestClient rest)
at PasswordManagerAccess.Bitwarden.Client.Login(String username, Byte[] passwordHash, String deviceId, IUi ui, ISecureStorage storage, RestClient rest)
at PasswordManagerAccess.Bitwarden.Client.OpenVault(String username, String password, String deviceId, String baseUrl, IUi ui, ISecureStorage storage, IRestTransport transport)
at PasswordManagerAccess.Bitwarden.Vault.Open(String username, String password, String deviceId, String baseUrl, IUi ui, ISecureStorage storage)
at Devolutions.RemoteDesktopManager.Managers.BitwardenManager.c2b5cd6838c9b19c2e1e62f246f08131c.c5dd20686dcb6fc762f9a873101f19386()

Me too - same error in Application log - ersion is ENTERPRISE EDITION 2021.1.30.0 64-bit

PasswordManagerAccess.Common.InternalErrorException: Network request or response parsing failed ---> Newtonsoft.Json.JsonReaderException: Unexpected character encountered while parsing value: e. Path '', line 0, position 0.
bei Newtonsoft.Json.JsonTextReader.ParseValue()
bei Newtonsoft.Json.JsonTextReader.Read()
bei Newtonsoft.Json.JsonReader.ReadForType(JsonContract contract, Boolean hasConverter)
bei Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(JsonReader reader, Type objectType, Boolean checkAdditionalContent)
bei Newtonsoft.Json.JsonSerializer.DeserializeInternal(JsonReader reader, Type objectType)
bei Newtonsoft.Json.JsonConvert.DeserializeObject(String value, Type type, JsonSerializerSettings settings)
bei Newtonsoft.Json.JsonConvert.DeserializeObject[T](String value, JsonSerializerSettings settings)
bei Newtonsoft.Json.JsonConvert.DeserializeObject[T](String value)
bei PasswordManagerAccess.Common.RestClient.MakeRequest[TContent,TData](String endpoint, HttpMethod method, HttpContent content, Dictionary`2 headers, Dictionary`2 cookies, Int32 maxRedirects, Func`2 deserialize)
--- Ende der internen Ausnahmestapelüberwachung ---
bei PasswordManagerAccess.Bitwarden.Client.RequestAuthToken(String username, Byte[] passwordHash, String deviceId, SecondFactorOptions secondFactorOptions, RestClient rest)
bei PasswordManagerAccess.Bitwarden.Client.Login(String username, Byte[] passwordHash, String deviceId, IUi ui, ISecureStorage storage, RestClient rest)
bei PasswordManagerAccess.Bitwarden.Client.OpenVault(String username, String password, String deviceId, String baseUrl, IUi ui, ISecureStorage storage, IRestTransport transport)
bei PasswordManagerAccess.Bitwarden.Vault.Open(String username, String password, String deviceId, String baseUrl, IUi ui, ISecureStorage storage)
bei Devolutions.RemoteDesktopManager.Managers.BitwardenManager.c2b5cd6838c9b19c2e1e62f246f08131c.c5dd20686dcb6fc762f9a873101f19386()

Hello,
We have made a potential fix in RDM 2021.1.31.0:

https://remotedesktopmanager.com/home/download

Regards

Awesome. Seems to be working so far, so good. Thank you.

Works for me too.

Works for me too.

Thanks

works, but is too slow to work with it.

To open a session with bitwarden msf need 45 sec.
To show a password without mfa need 15 sec.

I can't work now with RDM & Bitwarden.

br
Johann

sorry for me finger.

• To open a session with bitwarden mfa need 45 sec. (stop only the time, where I wait)

br
Johann

Hello,

@Johann: During our testing, it was sometimes slow since the Bitwarden server itself was slow to respond. This is out of our control, as it even affected their official CLI. Do you still experience slowness with the integration in RDM? Maybe they are still having server issues.

Regards,

Hello

today I tested and I have the same time issue.

Bitwarden without 2FA is finsihed in 15 sec.
Bitwarden with 2FA - the window for TOTP selection need 40 sec. and after insert the digits need ca. 5 sec.

if I logon in browser by bitwarden then it work under 1 sec.

br
Johann

Hello Johann,

We've been testing on our end and we still aren't reproducing the slowness issue, with or without 2FA. For us it goes really quick, around 1-2 seconds, same as the web-based Bitwarden vault.

If you're still reproducing today, could you tell us what region of the world you're located in? North America, Europe, Asia? Maybe we're having issues when the requests come from certain regions of the world.

If it's possible for you, it would be useful if you could try using the official Bitwarden CLI as well, and see if you have the same kind of issues using it. Here is Bitwarden's help topic on the subject: https://bitwarden.com/help/article/cli/

Regards,

Hello

I download the Bitwarden CLI for windows and test the login, from ENTER to see ? Two-step loin code need 35 sec.

I install everthing on a other laptop, that I can check.

My location is Europe \ Austria

br
Johann

Hello,

Thank you for doing the test. Unfortunately if the issue also occurs for you with the Bitwarden CLI, it points to an issue with their servers and not with the RDM integration.

I would suggest contacting Bitwarden's support team to see if they can help you out with the performance of the Bitwarden CLI. Since we use the same kinds of APIs, I suspect that if they provide a solution regarding the CLI, it will also affect us with the integration.

As a note we have also tested in a European location, we had your issue a few days ago, but since then it was fixed for us. It really points towards intermittent server issues, which we are unable to help with.

Regards,

I also get the message "Unable to retreive Bitwarden credentials". My bitwarden account was created 3 weeks ago and started working with the "Remote desktop manager" around the same time.

At first i had this issue and i reinstalled the RDM Software and the issue was gone.

Unfortionatly this morning the issue has reapeared.

My company has a premium licence for bitwarden and i use the APi key to make a connection between bitwarden en RDM.
I have already reconfirmed the API key's.

p.s. Bitwarden works for 2 other colleagues just fine there installation has been in place for a few months already.

Hello,

Could you check in your application logs what the underlying error is? We have received a few messages for issues relating to Bitwarden. You can check over at this thread: https://forum.devolutions.net/topics/38867/bitwarden-problems--same-user-vault-works-on-one-pc-not-on-another#172258

We had a fix for RDM 2022.3.33.0, but it seems that something else changed on the Bitwarden side and now it broke. We are currently investigating.

Regards,