Compass
36 results found
-
Improve Compass experience for working with lots of Atlas Clusters
Currently it's quite a lot of work to onboard Atlas Clusters especially if you have a lot. We have 80+. It would be a great if there was an easier way to create Cluster connections within Compass, whether that be an export/import process or you just connect it to Atlas and it works it all out via an API.
To further support this it would also be great to set username/password details and preferences like secondary at root or group level so that clusters under root or group can inherit those credentials rather than filling in for each connection
2 votes -
warn about stale IP address whitelisting
For people who work on wireless networks, if you come back after the weekend the IP address has often changed. If you are working with whitelisting, you now have the surprising situation that your connection string no longer works.
The sidebar in Compass gives instructions on getting the connection string or how to format it, but no reminder that connections that recently worked might be unusable now because the IP address whitelisting is now out of date.
In addition, Compass might list your IPv4 and IPv6 to let you know what these values are instead of requiring to go to…
1 vote -
Explicit confirm the saving of connection credentials
When user enter connection info, the details are saved for the next time.
If the user want to forget the info he need to disconnect and then remove the connection string.
Instead i suggest that only when the user explicitly ask to save the connection string (with checkbox atc.) the connection will be available for the next opening
1 vote -
Support SSH tunnel to Atlas with AWS Private Endpoint
Compass cannot connect via ssh tunnel with SRV connection string when the MongoDB server is behind Private Endpoint.
looks like Private Endpoint appear 3 different ports for each replica.
3 votes -
Support discovering deployment topology
It appears that Compass has no provision to discover the topology of deployment, and instead it requires the user to specify replica set name in order to connect to a replica set.
This was mentioned on SO here: https://stackoverflow.com/questions/61135528/mongodb-compass-forces-me-to-enter-replica-set-name-when-trying-to-connect-to-my/61135731#61135731
For example when I connected to mongodb://localhost:27020 where the node at 27020 is a secondary, I received this message:
An error occurred while loading navigation: 'not master and slaveOk=false': It is recommended to change your read preference in the connection dialog to Primary Preferred or Secondary Preferred or provide a replica set name for a full topology connection.
As a user…
1 vote -
SSL - Allow access to Trusted Root Certification Authorities in Windows
Allow Compass to access the Trusted Root Certification Authorities Certificate Store in Windows to be able to connect via SSL with a system-wide root CA file (without explicitly specifying the CA file).
2 votes -
Compass
I'm having problems with Compass. I create 2 connections.
One to connect to DB to practise - Chapter I
Another connection to connect to my Sandbox clusterBoth of them have different hostnames
When I Exit y Open Compass again, the favourites are no more I need to create the connections again. Before updating, I haven't this problem
How can I solve?1 vote -
Require user confirmation before saving over a favorite connection
Currently if you accidentally click "Paste connection string" on a saved favorite connection, all the manually inputted and saved connection settings will disappear. A favorite connection should not be edited until the user explicitly confirms it should be saved. It's extremely frustrating to have to reconfigure a "saved" connection due to clicking on something that gives no indication it will modify the saved settings at all
1 vote -
I would like to name an "Alias" for my MongoDB connections
I have many MongoDB Connections in my Compass in different ports. But it would be nice if I could identify then.
2 votes -
when I press connect, it keeps charging forever
when I press connect, it keeps charging forever
1 vote -
Have option to make "Fill in connection fields individually" view the default upon start up
Currently, MongoDB Compass defaults to showing the "Paste connection string" view upon startup. The full connection string is shown, meaning that if you have any saved favorites, the username and password will be immediately visible upon the screen. This seems like a security risk, especially for use in public settings.
Additionally, if your saved favorite includes SSH tunneling settings, these settings will not be applied if you try to connect to the database from the "Paste connection string" view, leading to connection failure. You must switch to the "Fill in connection fields individually" view before hitting Connect for the SSH…
12 votes -
Fix bug with missing SSH passphrase
If you have a passphrase on your SSH key file, but neglect to fill in the SSH passphrase field when trying to connect, nothing happens when you click on "Connect". No error message, nothing. Took me a long time to figure that out.
1 vote -
Sort favorite connections by name
Right now it seems favorites are sorted by least recent created. When you have a bit more (I have 9) it would be great to have them sorted by name instead. Or otherwise, sort by most recent used, or allow to sort manually.
2 votes -
Folders/groups for favorites
Compass users with many deployments need the ability to:
- reorder favorites, possibly based on usage patterns, as well as,
- organize favorites into folders.
These features will allow users to efficiently access important connection favorites, even when there are a large number of deployments present.
36 votes -
I want to use Favorites without storing passwords
For the Compass saved "Favorites", is it possible to save the Fav specifically without the LDAP Password and the without the Client Key Password? Instead leave them blank as a favorite, so I can then enter them each time logging in?
The reason is if the MongoDb has PHI data, and if I lost my computer, a hacker could not just click to open and gain immediate access. Thank you.
24 votes -
Check if port is blocked by firewall
One of the first things students of the MongoDB who have issues connecting to Atlas with Compass are asked to do, is to ensure port 27017 is not blocked by their firewall.
The student is asked to navigate to: http://portquiz.net:27017/
It would be nice for Compass to integrate a similar check to guide the user a little more when they experience a connection issue.
1 vote
- Don't see your idea?