[COMPASS-3495] Compass 1.17.0 does not recognize Atlas connection string, multiple issues Created: 09/Mar/19  Updated: 11/Mar/19  Resolved: 11/Mar/19

Status: Closed
Project: Compass
Component/s: Atlas, Compass
Affects Version/s: 1.17.0
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Brian Blevins Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File copy_only_connection_string.png    

 Description   

There are at least two problems with connecting to an Atlas cluster using Compass version 1.17.0.

1. When attempting to connect to an Atlas cluster (1.12 or later, ie. SRV connection) using Compass 1.17.0, the string in the clipboard is not recognized. Compass does not present the "MongoDB connection string detected" dialog.

2. When using the hostname or "1.11 or earlier" (non-SRV) option, the authentication method is left at "None", which is incorrect for Atlas connections. Note that copying only the SRV connection string into the clipboard causes it to be recognize, but the authentication setting is also "None", so this issue is orthogonal to item #1.

These issues appear to related to recent changes in both Compass and/or the Atlas user interface.



 Comments   
Comment by Massimiliano Marcon [ 11/Mar/19 ]

The Atlas team will change back the connection string to what it should be.

Comment by Brian Blevins [ 09/Mar/19 ]

Workaround

You can still use the current Atlas connection string with Compass. Simply copy only the connection string portion to the clipboard before switching back to Compass.

Be sure to select Username / Password authentication and then provide your Atlas database username and password. At that point, you can provide a favorite name to create a favorite and/or click the green Connect button to access your Atlas cluster.

Generated at Wed Feb 07 22:33:21 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.