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
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
Billing should be limited to organization owners only and not viewable by the entire organization.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
When logging into the support portal using support.mongodb.com, if federation is enabled, the user is redirected to their identity provider based on their domain, authenticated, and then redirected to the support portal.
However, if the custom URL for the identity provider is used, the user is always redirected to the Atlas interface. We would like to request that this custom URL be able to target an endpoint other than Atlas, such as the Support Portal.1 vote
- Don't see your idea?