Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
72 results found
-
Allow setting temporary IPs to API Access List
When testing out API keys that are normally only run through CI/CD tools, I'd like to be able to add my local IP to the API Access List for a temporary time window.
3 votes -
Support for User Groups with Separate Authentication Configurations
Currently Atlas only uses a single (flat) user group which only allows for 1 type of authentication per Organization.
However if Federated Authentication is enabled, the authentication mechanism in Atlas is bypassed for the IdP based on the domain name of the user and the configuration of Atlas Authentication.
This causes a problem if there are multiple groups of users who all share a domain name, some of whom are registered in an IdP, and some of whom are not registered in an IdP (for example users in 2 divisions of the same company).
In this scenario, users who are…
25 votes -
Migrate users and roles with cluster data
It would be great to be able to transfer users with their credentials and permissions from our on-premises deployment to Atlas during migration to avoid having to recreate those users using the Atlas interface or API.
22 votes -
Improve password manager support on login screen
Currently on the Atlas login screen it presents a button to authenticate using Google and a text field to enter an email address. Upon entering an email address there's a brief pause - presumably to check if the email address is bound to a configured SAML provider - and if not then the password field appears.
Since the password field doesn't exist in the DOM until it's needed it means password managers have to autofill the email and password fields as two separate steps. I propose to have the password field present and hidden from the start so that password…
3 votes -
Projects Organization
It would be great if we could organize the projects and not have them all at the same level of organization.
We could use this hierarchy to put rights, consult costs ...
A bit like the idea of Azure's management group or GCP's "Folder".25 votes -
Expose the killOp() action when creating custom roles in Atlas UI
It would be nice to have the
killOp()action exposed when creating a custom role in Atlas.I also think it would make sense to grant this action to the
atlasAdminrole, but at a minimum I feel that Project Owners should be able to create a custom role that is allowed to kill ops that were initiated by other database users.16 votes -
My entire team receives the billing info every month.
Billing should be limited to organization owners only and not viewable by the entire organization.
5 votes -
Federation metadata.xml for automatic idp certificate rotation
It would be great to have an opportunity to automatically rotate the idp signature certificate.
I could provide a metadata.xml url. With that metadata.xml in generally it's possible that okta rotate the certificate on it's own. But it's not possible to configure in Mongodb Atlas.
Best regards
Fabian1 vote -
Teams API should show the projects the team is a member of
Right now the API to retrieve information of a team ( either by ID or by Name ) only gives the name, the id and a link of the specific team.
I would like to see to what projects a team has access with which permissions ( as you can see via the atlas console ).
This would help a lot with automating access management
2 votes -
API Improvements - OpenAPI and more auth options
The API should be documented with OpenAPI to allow better tooling.
Ideally using the above OpenAPI spec you could auto generate a SDK or API client for popular languages.
Lastly, the API should accept authentication options other than digest. There is very poor support for digest authentication by popular HTTP clients. I don't like trying to implement security protocols myself, as there is often some quirk I have not fully understood that ends up leaving me less secure than I hoped.
In many questions online when searching for information about digest authentication, the person asking the question is asking about…
12 votes -
Project Monitoring Admin -- Access
Hi Team,
We need to give access to a particular team so they can create, edit, clone, disable, and delete the alarm for the entire organization in Alert setting only.
We should not give them access other than the Alert setting. Is there any way to give access for Alert setting only, kindly provide your suggestions at the earliest.
Please provide us steps if there's any way to create custom access for alert settings alone.
5 votes -
Make session timeout in Atlas UI configurable
Session timeout value in Atlas UI defaults at 12h. Allow it to be configurable per Project or Organization, with the minimum value being 15 minutes. All Atlas users within an organization that have been idle for the duration of the configured session timeout should be automatically logged out.
38 votes -
Atlas console authentication logs
MongoDB Atlas does not seem to provide a tool or a page that will show the authentication logs for the Atlas console users. Example - a log indicating when a project owner or a cluster manager logged in or out of the Atlas console along with the relevant time stamps.
I have raised a support case with MongoDB and the engineer suggested to raise a feature request as this feature is currently not available. Refer case #00755619.
Thank you.
1 vote -
Allow Atlas User Data Access Permissions to be configured on a per-database/collection basis
Similarly to how database user data access permissions can be configured on a per-database or per-collection basis, it would be ideal if Atlas user data access permissions (as they apply to Data Explorer) could be configured on a more granular basis as well.
8 votes -
Via API call invite existing atlas user & assigne them to project & teams
in are organization we want user to have a self serve service that allow them to create project, cluster ,etc ...
for now we can only automate half of the process, because we need the web UI to invite user & wait that they approve the invitation before assigning them to project.
It would be great than we could, via API call, invite user & assign them to project or team without having to use manual process & wait for user to acknowledge the invitation
thanks
11 votes -
Allow me to stay logged in for a long period of time
I access Mongo Cloud / Atlas very frequently. However, almost every day I need to re-login using my Google account. It doesn't seem to "remember" my session.
I would love if I can extend the default, and let me (and other members) stay logged in for a longer period of time.14 votes -
Improve 2FA and auth management
Right now, there is no way to require Google auth or to require 2FA. The only way to enforce 2FA for a team is to check the team mangagement page. However, since some users may have only used Google auth to login, they will show up in this view as not having 2FA, creating auditing headaches. Please
- indicate if a user does not have 2fa because they do not have a password vs just not having 2fa
- ideally, add the ability to require 2fa and/or Google auth for all team members10 votes -
Filter users list by organization role
The Users view in the Access Manager really needs a way to either sort or filter by role, so I can see a single screen with just the users who are Owners, for example.
2 votes -
Domain Validation should use subdomain rather than domain root
When entering the txt value for validation atlas should use its own subdomain for the verification rather than requiring the domain root which is often populated with spf keys.
Other examples of this implementation are
Github: github-challenge-org.domain.com
Mandrill: mandrill.domainkey.domain.com
Google: google._domainkey.domain.com1 vote -
Ability to customize the name of the invite sender in emails when inviting users via API
When inviting new Atlas Users to organizations via the API, the invite email says that the invite was sent by the API public key that performed the API call. This makes the invitation emails read like this:
"You have been invited by tfqzvwrs to join the Example - Atlas organization on MongoDB Atlas."
The ability to customize this (e.g. using an additional field in the request body) would be ideal since the random string being shown as the sender of the invite could make the email look suspect.
1 vote
- Don't see your idea?