Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
75 results found
-
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 -
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 -
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 -
Change Username
Ability to change your username after registration and be able to re-use it should you need to.
5 votes -
Day granularity for Atlas-managed X.509 certificate
It would be great to add more granularity when creating an Atlas-managed X.509 certificate for a MongoDB user, i mean by day at least.
Thank you6 votes -
Way to enforce 2FA across organisation
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 management
1 vote -
Add privileges for Custom Roles which are currently only available in Built-in Roles
Currently the list of privileges assignable for Custom Roles is only a subset of privileges available to Built-in Roles This request is to add the missing privileges to both the REST API and Atlas UI which are available to Built-in Roles
The first set of privileges requested by a customer is from the Cluster Monitor role
Expanded prioritized privileges requested:
checkFreeMonitoringStatus
getCmdLineOpts
getLog
getParameter
getShardMap
hostInfo
inprog
listShards
netstat
replSetGetConfig
replSetGetStatus
setFreeMonitoring
shardingState3 votes -
Privilege advisor capability
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 -
remove the captcha from login, especially if 2 factor auth is enabled.
I very much dislike being asking to train ML models by doing picture identification just to login to my account. Please find a less offensive captcha process, or remove it entirely when 2 factor auth is enabled.
7 votes -
Stitch - use the same function to resend confirmation as when initially signing up
When signing up with Email/Pwd, one of the options is to have the confirmation run through a function.
In that function, a call to an external email provider has been set up to use a template with a logo.However, the "token" & "tokenId" parameters provided in the link are only valid for 30'.
This makes it likely for people to be too late to confirm their email address.
When calling "resendConfirmationLink", an email with a new link will indeed be sent out, but this is the standard MongoDB email. This request is to have this "resend" use the same…
3 votes -
Ability to change First and Last Name
It would be good if users are able to modify their First and Last Name after account creation.
7 votes -
) 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 -
Add Option to Disable Federated Authentication Automatic Account Creation
Based on the documentation it appears there is no option available to disable automatic account creation when Federated Authentication is used.
The business case for disabling automatic account creation is to allow a limited set of users from the Identity Provider to have access to Atlas and the databases, while not allowing anyone with an account in the same domain to create an Atlas/Database account.
2 votes -
Allow direct access to support portal when using custom federation URL
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.
2 votes -
Allow setting up 2FA when loggin in...
Hello would you guys implement 2FA when logging in on feedback website(here) without being logged in anywhere else with the password, i really need it for security reasons...thanks
2 votes
- Don't see your idea?