Robomongo: Unable to connect to Azure DocumentDb

Created on 21 Sep 2016  路  10Comments  路  Source: Studio3T/robomongo

Hi
I am unable to connect to Azure DocumentDb - I know i need to use SSL, but I don't know what certificate file should i use. There is no possibility to skip certifcates.
On MongoDb Compass there is a "use unvalidated SSL" option

Can you add such an option?

critical-connectivity needs investigation

Most helpful comment

Oh, I see it now :) Here it is, it is exactly the same as reported above:

image

All 10 comments

Hi @tomaszglinski, thank you for reporting! Am I correct assuming that you need something like --sslAllowInvalidCertificates? If so, you can just select Authentication Method as "Self-signed Certificate" on the SSL tab.
image
If I'm not correct, could you please share more details about error or case you get?

Hi Julia, thanks for reply.
Here is my error screenshot.
With the same credentials I can connect to the Azure through Sping Boot
application. In this app, in connection string there is only useSSL flag
set to true.
Does it help? Maybe you could try with some free Azure account if there is
any?
image

@tomaszglinski Thanks for sharing! At least, could you please send error detail (click the link "Show error details" on your shared diagnostic connection window)?
Sure, we'll start investigation soon and get back to you with any news.
Thank you!

@juliashibalko, will I look like a newbie if I ask what you mean with "shared diagnostic connection window"? :)

In the mean time - instead of using "Test connection" button I just used "Connect". I got the error:
_SSL connection failure: invalid salt length provided_

I think that would be some hint?

@tomaszglinski it's ok! Sorry, my answer was not clear. But you hit the mark with sharing error SSL connection failure: invalid salt length provided. That's what we need. Thanks a lot!
We have already started the investigation.

Great! Thanks for so quick response! Looking forward for a fix:)

Hi @tomaszglinski , while we are on the subject, for quick understanding better to get all debug information, can you click on "Show error details" on "Diagnostic" window on your error screen shot and share with us? Thanks.

Oh, I see it now :) Here it is, it is exactly the same as reported above:

image

Update:

  • Initial investigation shows that error comes from the code related to password handling.
    And it might be related to password length of Azure DocumentDb which is 89 characters lenght, there seems to be no way to change the password. It is auto generated.
  • So the issue seems to be not related to SSL but related to different config of Azure DocumentDb.

Next Actions:

  • Continue code investigation
  • Find a way to change user password for Azure DocumentDb
  • Plan official support for Azure DocumentDb.

I solve this problem when I use Azure button to copy password.

Was this page helpful?
0 / 5 - 0 ratings