Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
-
Manage Database Access and Network access
I would like to give colleagues the ability to manage Database Access and Network access for a project without giving the the project owner role.
A way to provide more granular access in Atlas would be nice
1 vote -
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.
1 vote -
1 vote
-
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 -
More Fine-Grained Custom Roles
Our developers need to access databases from home or an office location from time to time.
They are not Project Owners and should not have broad sweeping administrative privileges over the databases.
In some cases they may be outsource workers who would only have read-only views on the data.
However, they do need to be able to connect to the databases.
Currently, you need a Project Owner role to be able to add an IP address to the whitelist and allow remote access.
Please add the ability to create custom roles for Atlas users, which would enable us to create…2 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 -
Need access to the REST API for IdP Federation
Currently all IdP federation set up must be done in the Atlas GUI. This prohibits scripting the setup of IdP organization and role mapping for new projects.
Customers can prefer setting this up via a scriptable Rest API interface for a new project. Everything else about the project has an API that is currently used to create projects and deploy clusters. Authentication is important part of the process and currently requires manual set up through the GUI.
1 vote -
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…
2 votes -
make empty teams possible
It is currently not possible to create empty teams of remove all users from teams.
We would like to arrange our access management through teams. For our production environment we want a 'read only' and an 'admin' team. The admin team should be empty at all times, except in the case of incidents where we want to add specific users to the admin team to be able to solve the incident.4 votes -
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 -
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 -
more information in AWS IAM audit logs
We are using MongoDB-AWS for authentication, and have set up the audit log to log events taken by AWS roles. However, there is insufficient information in the logs to identify who is doing those actions, as roles can be assumed by multiple people.
An example log line in the current audit log:
{ "atype" : "authenticate", "ts" : { "$date" : "2021-01-05T00:21:52.628+00:00" }, "local" : { "ip" : "192.168.248.203", "port" : 27017 }, "remote" : { "ip" : "172.31.0.5", "port" : 54195 }, "users" : [ { "user" : "arn:aws:sts::555555555555:assumed-role/developer-role/", "db" : "$external" } ], "roles" : [ {…2 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.
1 vote -
Allow modifying federation role mappings via API
We would like to use the new role mapping feature for federated authentication to assign Atlas roles based on LDAP groups assigned to our users.
However, we frequently create new projects programmatically and would need to manage the permissions to these new projects using role mapping. However, there is no public API available to manage role mappings programmatically. In addition, enabling role mapping disables the ability to manage roles for federated users with the API. So, at present, role mappings and permissions can only be managed manually through the UI.
We would like to request the ability to modify role…
3 votes -
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 -
Authentification on Azure (IAM)
Hello,
We absolutely need a more modern authentication method than using LDAPS to authenticate users against the MongoDB databases that we deploy with Atlas. When will we see a modern authentication service at this level? Ideally, we want cloud functionality equivalent to AWS IAM but on Azure.
1 vote -
Ability to invalidate or revoke a X.509 certificate that was not expired.
Currently, X.509 certificates can be issued for authentication and authorization. However, it is not possible to invalidate an already issued certificate. In a situation where the certificate would be compromised, it is therefore not possible to invalidate it and re-issue a new one. The only way is to delete the user associated with the certificate and create a new user account (New CN).
1 vote -
My entire team receives the billing info every month.
Billing should be limited to organization owners only and not viewable by the entire organization.
1 vote -
Support GCP IAM for Cluster Authentication
Achieve feature parity with AWS IAM cluster authentication support.
42 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.
3 votes
- Don't see your idea?