In our software development lifecycle, we have sprints that are 2 weeks long.
We create temporary users for Software Engineers that are "onCall" during a sprint. The role is moving to a different engineer each new sprint.
It would be great to be able to specify an explicit
deleteAfterDatevalue or a custom duration greater than the current 6 days.1 vote
if this limit is reached, mongodb throws error1 vote
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 nice1 vote
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
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
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
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?