74 results found
Warn when attempting to add a new IP address to network access that is already covered by an existing entry
Currently, if one tries to add a new IP address to the list of whitelisted IPs for a database in the 'Network Access' page, and the new IP is a duplicate of an existing entry, there is no warning or indication given to the user, and the list of IPs remains unchanged.
This makes it seem like the button to add a new IP doesn't work, as the list of IPs doesn't change.
So there should be some indication that the user attempted to add a duplicate IP, and because of that, the list of allowed IPs was not changed.1 vote
There are many new web developer come on MongoDB Atlas. There create there account and start working but don't know any thing about MongoDB. Something goes wrong on there setup and decided to recreate there account and follow all the instructions. But after deleting there account they see that they can't use there old email address.
Because of this situations that I faced. I don't want these to be faced by someone else so I recommend MongoDB Atlas to remove this security policy. Guys, Do you support me?1 vote
When login to Atlas, we can use Google Login at the moment.
Please add Login with Microsoft Credentials.1 vote
When managing accounts and permissions, it could be great to "disable" an account before deleting it or reseting its password.
By example GCP ServiceAccounts have this feature. It helps to restore a service of an account faster if this one is still in use.
It will also help to set a kind of "policy" where inactive accounts get deactivated for a period of time and then deleted if not reactivated till then.1 vote
if this limit is reached, mongodb throws error1 vote
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.
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
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
Google: google._domainkey.domain.com1 vote
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
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
It would be incredibly helpful to have some sort of capability that allows users within the Atlas portal to be able to see what privileges are needed to perform various actions. For example, we have users that are not able to configure alerts, or other users that are not able to add users to a project. It isn't always clear what privileges are needed in order to give users those capabilities. Either some sort of tool would be helpful, or very clear documentation on privileges that are needed for each capability within Atlas.1 vote
Please add the capability to enforce 2FA (As a setting) for any user invited to join a team. This would be a good step towards better security management1 vote
) User A login inot Mongo Portal 2) He selects an organization and sends an invitation to User B 3) Now in the Activity Feed menu we can see
1)User A login inot Mongo Portal
2) He selects an organization and sends an invitation to User B
3) Now in the Activity Feed menu we can see User B was invited to the organization
4)Before the user B accepts the invitation , User A goes and deletes the pending invitation
5)Nothing is shown in activity feed.
This would help products which are integrating with MongoDB atlas to get the true status of pending invitations.1 vote
- Don't see your idea?