Compass
47 results found
-
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.
46 votes -
Allow connections to Atlas from Compass using SAML/SSO
When using Atlas with SAML (e.g. Okta, AzureAD) there is no (obvious) way to get access to the Atlas Cluster from Compass. Following the Compass instructions to get the username/connection string from Atlas shows me the shared SAML user - whom I cannot and should never get the password for - and no way to get the token or whatever it is that SAML is doing under the hood.
Can Compass please have a SAML option added - open a browser to the SSO provider and capture what it needs from there?
27 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.
26 votes -
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 -
AWS IAM in Compass is MFA protected & uses shortly expiring tokens
AWS IAM auth in Compass should be a password/token-copypaste-less, MFA-protected experience that uses shortly-expiring tokens, invisibly to the user. Said differently, selecting AWS IAM creds should prompt me with an { AWS config, MFA challenge } form/flow, and not an {{{ accessKeyId, secretAccessKey, sessionToken }}} form as it does today.
5 votes -
Store Atlas Login Creds in Compass
If i want to use mongo generate query feature, i need to login to atlas everytime. Need compass to store the login creds and auto login.
3 votes -
Need "Inactive" sessions "Terminated" connected via Compass to MongoDB
Need "Inactive" sessions "Terminated" which have been connected via Compass to MongoDB and idle for more than x minutes. This feature is not full available. As per MongoDB support maxIdleTimeMS -- "Compass supports that option but please note that this won't close the session, will only collect idle connections in the pool and wouldn't really be noticed on the user end.
For you to be aware, this request was already discussed internally as a missing option so it would be good if you can provide some additional feedback in our official website for our Product managers to consider."3 votes -
Provide an UI option to limit Compass to a single database connection by setting the maxPoolSize to 1 in the driver
There are some authentication setups in the field that require customers to approve every attempt to use their external credentials (such as LDAP passwords) via manual interaction with an MFA vendor's app (a good example would be Okta Verify).
When the driver has a connection pool greater than 1 (the current default is 10), it may spawn additional connections to the database without letting the customer know. This may result in authentication failures for the various commands - if the customer misses the MFA prompt on their device.
The current solution is to set the maxPoolSize=1 option in the connection…
3 votes -
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 -
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).
3 votes -
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.
3 votes -
Removing a connection needs to show you a confirmation dialog
Removing a connection needs to show you a confirmation dialog
2 votes -
2 votes
-
MongoDB Compass can have a Account Section
MongoDB Compass can have a option to sign in so that users can log in to their account can directly access their Atlas Clusters without having headache to get connection string and paste it here
2 votes -
Support ssh certificates when connecting via ssh
Per this forum post https://www.mongodb.com/community/forums/t/ssh-certificates-with-mongo-compass/204504 Compass does not support the use of ssh certificates.
2 votes -
Recognize $HOME/.ssh/config file in SSH bastion / jump box
Configured hostnames are not read from the file causing the user to have to re-input the same jumpbox information per connection.
The work around is to define jumpbox destinations on the user's /etc/hosts file but preference is to have Compass respect the default SSH config file.
2 votes -
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 -
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 -
IAM Connectivity using Mongo Compass
Description:
It would be helpful to integrate AWS IAM profiles directly into MongoDB Compass. Users should be able to read the available AWS IAM profiles from their AWS CLI configuration, select one from a list, and connect seamlessly without the need to manually copy the access key ID, secret key, and token.Current Limitation:
At the moment, users must run an AWS CLI command to manually retrieve and input their credentials into Compass. This process is very frustrating, especially since users have to copy and paste the tokens every single time they want to connect.Suggested Improvement:
Enable MongoDB Compass…1 vote -
Secure my connections
Make connections more secure by asking for a password or passphrase every time I click 'connect' on any of my already saved connections. Each connection should have, like a 'security configuration' dialog or something, where you can set and/or update password for that connection.
1 vote
- Don't see your idea?