73 results found

1. More documentation about alert

   It would be great if there were a doc explaning what each Alert Event Types means (and even that could give us some examples). And the same documentation should explain wich alerts have thresholdconfig or metricthreshold_config.

   The documentation that I have found with a little explanation is thw below (and it shows some alerts type that don´t work)
   Example: OPLOGBEHIND => When trying to use this one on terraform, it returns an error saying it does not exist (the one that works is: REPLICATIONOPLOGWINDOWRUNNING_OUT)

   https://www.mongodb.com/docs/ops-manager/current/reference/alert-types/#user

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Alerts  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. MongoDB to throw error when detect '.' in keys insert

   Not sure if MongoDB was supposed to be unstructured even for keys. Because MongoDB currently does not support '$' and '.' in its keys, is it possible for MongoDB to throw an error if '$' or '.' are detected in keys during insert? MongoDB currently does not do that and is problematic to fix for previous large databases which have '$' or '.' in keys

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Data Explorer  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Azure VNet terminology needs updating

   Setting up the Peering Connection (Project Network) has antiquated terminology and instructions.

   Microsoft Entra ID is the new name for Azure AD. The names Azure Active Directory, Azure AD, and AAD are replaced with Microsoft Entra ID. Microsoft Entra is the name for the product family of identity and network access solutions. Microsoft Entra ID is one of the products within that family. https://learn.microsoft.com/en-us/entra/fundamentals/new-name#:~:text=Microsoft Entra ID is the,the products within that family.

   The name change took place on July 15, 2023. https://learn.microsoft.com/en-us/azure/active-directory/fundamentals/new-name

   Currently:

   Directory/Tenant ID

   This is a 32-character alphanumeric string. Find this in the Azure portal in Azure Active Directory / Properties. Show Instructions

   Navigate to Azure Active Directory / Properties. Your Directory/Tenant ID is shown under Directory properties.

   Setting up the Peering Connection (Project Network) has antiquated terminology and instructions.

   Microsoft Entra ID is the new name for Azure AD. The names Azure Active Directory, Azure AD, and AAD are replaced with Microsoft Entra ID. Microsoft Entra is the name for the product family of identity and network access solutions. Microsoft Entra ID is one of the products within that family. https://learn.microsoft.com/en-us/entra/fundamentals/new-name#:~:text=Microsoft Entra ID is the,the products within that family.

   The name change took place on July 15, 2023. https://learn.microsoft.com/en-us/azure/active-directory/fundamentals/new-name

   Currently:

   Directory/Tenant ID

   This is a 32-character alphanumeric string. Find this in the Azure portal in Azure Active… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Other  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Please clean your mind

   What i mean is for newbie mongodb is trash , I am full stack dev and i have to use this for complete mern project and how we gonna do that => by watching video tut which you guys but you guys change syntax every year that makes impossible to work on ongoing project.
   So I somehow arranged to have mongodb in my mac m1 then bloody xcode did some changes now again errors after error .
   So I somehow thought I should use atlas atleast i will not be in my system and guess what you guys changed some **** again
   
   {
   mongoose.connect(connection_string, {
   useNewUrlParser: true,
   useCreateIndex: true,
   useUnifiedTopology: true

   })
   }
   This one !!
   https://www.mongodb.com/community/forums/t/option-usecreateindex-is-not-supported/123048
   So now deleted that project and wish to never hear mongodb in my life again and you guys can change the syntax in meantime !!
   Because everytime it took around 8 hr to know what the **** is wrong with that error.
   Please syntax is not like climate that you change every year.

   What i mean is for newbie mongodb is trash , I am full stack dev and i have to use this for complete mern project and how we gonna do that => by watching video tut which you guys but you guys change syntax every year that makes impossible to work on ongoing project.
   So I somehow arranged to have mongodb in my mac m1 then bloody xcode did some changes now again errors after error .
   So I somehow thought I should use atlas atleast i will not be in my system and guess what you guys changed some… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Tutorials/How-tos  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. I can not access the collections in cluster, again and again it showing error
   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. [Bug?] Attempting to pin Feature Compatibility Version (FCV) without appropriate permissions silently fails

   When attempting pin FCV on a cluster without sufficient account permissions via the UI 0, it silently fails and does not show any feedback to the user.

   The network response is a relatively generic 403 Forbidden error.

   Support noted that a user must have the "Project Owner" permissions to do so and to reach out to the Org Owner to get elevated privileges.

   Ideally the UI should actually notify the user that this is the case.

   ---

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Copy/Duplicate Cluster configuration

   It would be really useful to create a new cluster based on an existing configuration.

   Snapshots are supposed to be loaded into clusters of the same configuration, but having to set up the configuration manually is prone to human error. Having an option to copy the cluster configuration would be helpful.

   Support suggested the following workarounds, but the option should really exist in the UX, given that snapshots can be taken and loaded in the UX.
   - use the API to create all clusters so that the config exists in code
   - use terraform to create clusters

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Allow to change defaultWriteConcernSource to global to avoid flipping the flag

   Customers experience following error messages due to the defaultWriteConcernSource mismatch between the source and target cluster when restore the snapshot.

   Error: Can not restore a snapshot with custom default write concern 1 to a cluster that does not have a custom default write concern.

   Error: Can not restore a snapshot with custom default write concern majority to a cluster that does not have a custom default write concern.

   Ability to directly change the defaultWriteConcernSource without flipping between w:1 and w:majority will be convenient for the users.

   Option location:

   Cluster > configuration > Additional Settings >
   More Configuration Options > Default Write Concern

   Thanks.

   Customers experience following error messages due to the defaultWriteConcernSource mismatch between the source and target cluster when restore the snapshot.

   Error: Can not restore a snapshot with custom default write concern 1 to a cluster that does not have a custom default write concern.

   Error: Can not restore a snapshot with custom default write concern majority to a cluster that does not have a custom default write concern.

   Ability to directly change the defaultWriteConcernSource without flipping between w:1 and w:majority will be convenient for the users.

   Option location:

   Cluster > configuration > Additional Settings >
   More Configuration Options > Default… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Backup  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. There is a grammatic error in button text.

   The button says "Do not me show again"; it should say "Do not show me again".

   Thank you,
   Alpesh

   •  

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Other  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Specify allowed values for fields in AWS CDK

    Example create database user:

    • Allowed values for databaseName are admin or $external in Admin API documentation (https://www.mongodb.com/docs/atlas/reference/api-resources-spec/#tag/Database-Users/operation/createDatabaseUser)
    • Corresponding CDK construct property (https://constructs.dev/packages/@mongodbatlas-awscdk/database-user/v/1.1.0/api/CfnDatabaseUserProps?lang=typescript#property.databaseName) only specifies string without further information

    It would be nice to get IntelliSense in IDEs for fields which are enums behind the scenes.

    Alternatively, allowed values should be included in error messages. That would make debugging at runtime easier at least.

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  CloudFormation Resources  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Ideally migration of terraform state should be handled or provide a tool for migrating state

    Hello,
    We initially rolled out all our clusters with mongo atlas terraform provider version 0.7.0. Since we hadn't pinned the version, we started seeing warning listed below in the terraform plan.

    Updating as indicated based on the warning means, a deletion and recreation of the private endpoint/link related resources which will lead to downtime as the cluster will be inaccessible while the private endpoint/link is being recreated.

    Ideally migration of terraform state should be handled or provide a tool for migrating state so the resource can be migrated without recreation.

    ============================================

    There are warnings related to your configuration. If no errors occurred,
    Terraform will continue despite these warnings. It is a good idea to resolve
    these warnings in the near future.

    Warnings:
    module.mongodbatlasds.mongodbatlasprivateendpoint.atlasprivateendpoint: this resource is deprecated, please transition as soon as possible to mongodbatlasprivatelinkendpoint
    module.mongodbatlasds.mongodbatlasprivateendpointinterfacelink.atlasprivateendpointinterfacelink: this resource is deprecated, please transition as soon as possible to mongodbatlasprivatelinkendpoint_service

    We did try using the import example but unfortunately ran into this issue:

    Error importing: Provider "mongodbatlas" depends on non-var "data.external.mongoatlasvaultcredentials.0/data.external.mongoatlasvaultcredentials.N". Providers for import can currently only depend on variables or must be hardcoded. You can stop import from loading configurations by specifying -config="".

    https://github.com/hashicorp/terraform/issues/17847

    Our provider configuration is something like this where it pulls the credentials from vault using a script:
    provider"mongodbatlas"{
    version="0.8.2"
    publickey="${data.external.mongoatlasvaultcredentials.result.publickey}"
    privatekey="${data.external.mongoatlasvaultcredentials.result.privatekey}"
    }

    Now just for the sake of trying, I did hard code the pubic key/private key in the provider for my dev dc and in that case, the import does work as expected. But since we have 10 data centers for which we have different keys, it's not possible for us to hard code anything since the same code is used for all the DCs. So even though the import option can work for a simple deployment test, it's not a working solution for us.

    Hello,
    We initially rolled out all our clusters with mongo atlas terraform provider version 0.7.0. Since we hadn't pinned the version, we started seeing warning listed below in the terraform plan.

    Updating as indicated based on the warning means, a deletion and recreation of the private endpoint/link related resources which will lead to downtime as the cluster will be inaccessible while the private endpoint/link is being recreated.

    Ideally migration of terraform state should be handled or provide a tool for migrating state so the resource can be migrated without recreation.

    ============================================

    There are warnings related to your configuration. If no … more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Terraform Provider  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. mongodbatlas_federated_database_instance add GCP support

    Is GCP support planned for terraform provider and GCP?

    dataprocessregion {
    cloudprovider = "GCP"
    region = "IOWAUSA"
    }

    Trying to use this in Terraform results in 500 Internal Server Error

    │ Error: error creating MongoDB Atlas Federated Database Instace: https://cloud.mongodb.com/api/atlas/v2/groups/***/dataFederation POST: HTTP 500 Internal Server Error (Error code: "UNEXPECTED_ERROR") Detail: Unexpected error. Reason: Internal Server Error.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Terraform Provider  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Enhanced Access to Secrets in the context.environment Object

    We would like to see an improvement where secrets can be accessed as environment variables directly through the context.environment object. For example, if we have a secret called myApiKey, we would like to be able to access it in a function using context.environment.secrets.myApiKey.

    This would make the process of storing and accessing environment-specific sensitive data like API keys, access tokens, etc., much more straightforward and error-proof.

    As it stands, we're creating a workaround by saving env specific API keys as secrets, and then using some logic with context.environment.tag to fetch the correct environment API key. However, this approach is not ideal as it adds unnecessary complexity and is not very intuitive.

    Storing environment-specific sensitive data is a common use case in almost every project. It seems like there should be a simple and straightforward solution for this.

    We would like to see an improvement where secrets can be accessed as environment variables directly through the context.environment object. For example, if we have a secret called myApiKey, we would like to be able to access it in a function using context.environment.secrets.myApiKey.

    This would make the process of storing and accessing environment-specific sensitive data like API keys, access tokens, etc., much more straightforward and error-proof.

    As it stands, we're creating a workaround by saving env specific API keys as secrets, and then using some logic with context.environment.tag to fetch the correct environment API key. However, this approach is not… more

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Have EventBridge send an error message to Atlas to stop flow of Trigger data at the source

    Currently, once a Mongo Trigger makes a successful hand-off to EventBridge, it doesn't have insight into EventBridge issues landing the data in its destination. Currently, you have to set up separate code to process failed EventBridge events using the DeadLetter queue. You also need to set up a process to integrate this data from the DeadLetter queue back into the EventBridge destination. If the requested functionality existed, you would only need the Trigger restart process to handle any failure in the data stream from Mongo to EventBridge destination. This will also enable a single place to monitor the data stream.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Integrations  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Better streamlined logs in GCP

    Running Application and MongoDB in the same public cloud provider. Want to have logs in one place so that in case of any issues, I can debug any production issues properly. For example, in our Development or local environment, we have everything running on Docker Desktop and MongoDB on local Windows laptop. Using Docker tilt - Dev team can see UI, Service tier and backend(MongoDB) logs one after the other in one place. If the request is timing out, we can see that it's a collection scan that is happening not index scan so we need to either create the index or fine tune our query or change the code - making it super easy. But in our GCP Production every thing runs in GCP kubernetes and logs are stderr and stdout of kubernetes and app but no mongoDB even when MongoDB is deployed within GCP. GCP support stated that we can install Google Cloud Ops Agent can be installed to forward the logs to GCP but it seems that won't work as there will be lag. We were told to do a lot of work to make it work which is error prone. It should be out of the box so that any users are not tempted to use cloud native DB solutions that comes with public cloud and still use MongoDB. Please refer Case #01336915

    Running Application and MongoDB in the same public cloud provider. Want to have logs in one place so that in case of any issues, I can debug any production issues properly. For example, in our Development or local environment, we have everything running on Docker Desktop and MongoDB on local Windows laptop. Using Docker tilt - Dev team can see UI, Service tier and backend(MongoDB) logs one after the other in one place. If the request is timing out, we can see that it's a collection scan that is happening not index scan so we need to either create the… more

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Support for CDK SAM Template in Publishing Serverless Applications in AWS

    I suggest that AWS supports CDK SAM Template for publishing serverless applications. Currently, when attempting to publish a serverless application using a SAM template that includes MongoDB Atlas CloudFormation extensions, such as MongoDB::Atlas::Project, MongoDB::Atlas::DatabaseUser, MongoDB::Atlas::Cluster, MongoDB::Atlas::ProjectIpAccessList, an error is encountered.

    Error Message:
    
Error: SAM template is invalid. It cannot be deployed using AWS CloudFormation due to the following validation error: Template format error: Unrecognized resource types: [MongoDB::Atlas::Project, MongoDB::Atlas::DatabaseUser, MongoDB::Atlas::Cluster, MongoDB::Atlas::ProjectIpAccessList]


    While deployments proceed smoothly, this error arises when attempting to publish the serverless application. It would be beneficial if AWS supports CDK SAM Template for publishing serverless applications, allowing for seamless deployment and publication processes.

    Thank you for considering this feedback.

    I suggest that AWS supports CDK SAM Template for publishing serverless applications. Currently, when attempting to publish a serverless application using a SAM template that includes MongoDB Atlas CloudFormation extensions, such as MongoDB::Atlas::Project, MongoDB::Atlas::DatabaseUser, MongoDB::Atlas::Cluster, MongoDB::Atlas::ProjectIpAccessList, an error is encountered.

    Error Message:
    
Error: SAM template is invalid. It cannot be deployed using AWS CloudFormation due to the following validation error: Template format error: Unrecognized resource types: [MongoDB::Atlas::Project, MongoDB::Atlas::DatabaseUser, MongoDB::Atlas::Cluster, MongoDB::Atlas::ProjectIpAccessList]


    While deployments proceed smoothly, this error arises when attempting to publish the serverless application. It would be beneficial if AWS supports CDK SAM Template for publishing serverless applications, allowing for… more

    •  

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  CloudFormation Resources  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Enable the use of the timeouts { ... } block in resource declarations.

    Enable the use of the timeouts { ... } block in resource declarations. I consistently get a timeout error on destroy of resources:

    Error: error deleting MongoDB Private Endpoints Connection(5e4e93f3c0073240658e5b1f): timeout while waiting for state to become 'DELETED, FAILED' (last state: 'DELETING', timeout: 2m0s)

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Terraform Provider  ·  Delete…  ·  Admin →
    completed  ·  AdminMelissa (Lead Product Manager, MongoDB) responded

    The timeout on this resource has been increased (https://github.com/mongodb/terraform-provider-mongodbatlas/issues/151) and since then we’ve seen no reports hitting the timeout before completion of the deletion. If this is encountered again please file an issue at https://github.com/mongodb/terraform-provider-mongodbatlas/issues/ letting us know what resource is hitting a timeout, what version of the provider and terraform you are using, and any relevant logs.

    Thank you!

18. need api endpoint to see current db user limit. also see this number in UI

    if this limit is reached, mongodb throws error

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  IAM  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Could we increase the vCPU's of the Atlas cluster without increasing its memory.(RAM)

    For example: suppose right now, we have 2 vCPU's with 8GB RAM. But we are facing high CPU utilization error. Can we change the vCPU's to 4 and keep RAM as it is i.e.8GB?

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Resource Tagging  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. SAML login on feedback.mongodb.com does not work with Google Auth

    It shows "SAML Error" and redirects the login page to cloud manager. As a result the login success is never passed to feedback.mongodb.com, it's necessary to login again (on the second attempt, it works)

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating