Atlas

Share your idea. In order to help prioritize, please include the following information

  1. A brief description of what you are looking to do
  2. How you think this will help
  3. Why this matters to you

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 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
    Sign in Sign in with: your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  IAM  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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
    Sign in Sign in with: your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  IAM  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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…

    2 votes
    Sign in Sign in with: your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  IAM  ·  Flag idea as inappropriate…  ·  Admin →
  4. Atlas API Enhancements

    Since we want to automate the user (de)provisioning for organizations and projects, we would like to see the following API enhancements:

    Please enhance the Mongo Atlas API for the following functionalities:
    - invite (existing mongo) user to organization (currently not possible)
    - remove user from organization
    - get invitation status from user
    - cancel invitation for user

    Thank you

    2 votes
    Sign in Sign in with: your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  IAM  ·  Flag idea as inappropriate…  ·  Admin →
  5. Via API call invite existing atlas user & assigne them to project & teams

    in are organization we want user to have a self serve service that allow them to create project, cluster ,etc ...

    for now we can only automate half of the process, because we need the web UI to invite user & wait that they approve the invitation before assigning them to project.

    It would be great than we could, via API call, invite user & assign them to project or team without having to use manual process & wait for user to acknowledge the invitation

    thanks

    2 votes
    Sign in Sign in with: your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  IAM  ·  Flag idea as inappropriate…  ·  Admin →
  6. Show all team users on one page

    When we do SOC2 reviews, we have to take screenshots of the permissions various users have. Currently, a specific "team" in Atlas only shows 5 users at a time and is paginated. Taking screenshots of 5 users at a time is pretty tedious, so it would be amazing to have a page with the full list.

    2 votes
    Sign in Sign in with: your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  IAM  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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
    shardingState

    2 votes
    Sign in Sign in with: your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  IAM  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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
    Sign in Sign in with: your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  IAM  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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
    Sign in Sign in with: your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    planned  ·  0 comments  ·  IAM  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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.com

    1 vote
    Sign in Sign in with: your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  IAM  ·  Flag idea as inappropriate…  ·  Admin →
  11. 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
    Sign in Sign in with: your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  IAM  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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
    Sign in Sign in with: your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  IAM  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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
    Sign in Sign in with: your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  IAM  ·  Flag idea as inappropriate…  ·  Admin →
  14. 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
    Sign in Sign in with: your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  IAM  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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
    Sign in Sign in with: your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  IAM  ·  Flag idea as inappropriate…  ·  Admin →
  16. 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
    Sign in Sign in with: your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  IAM  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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
    Sign in Sign in with: your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  IAM  ·  Flag idea as inappropriate…  ·  Admin →
  18. ) 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
    Sign in Sign in with: your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  IAM  ·  Flag idea as inappropriate…  ·  Admin →
  19. 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.

    1 vote
    Sign in Sign in with: your MongoDB Account
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  IAM  ·  Flag idea as inappropriate…  ·  Admin →
2 Next →
  • Don't see your idea?

Feedback and Knowledge Base