Geoffrey
My feedback
159 results found
-
8 votes
An error occurred while saving the comment An error occurred while saving the comment Geoffrey commented
Hello MongoDB,
We have a problem last week with Encryption at rest. MongoDB was not able to reach our Key Manager on Azure even it was available. MongoDB decide to shutdown our cluster for 3 hours. Do you plan to prioritize this feature request. Dont have this can compromize the usage of MongoDB in production.
See ticket: 00859378: Encryption at rest using Key stored in KeyVault failed
Geoffrey shared this idea ·
-
11 votes
An error occurred while saving the comment Geoffrey commented
Hello MongoDB. It is not too late to commit this feature for availability in the next version of your drivers. We would be very happy to try it soon. :-)
Geoffrey shared this idea ·
-
7 votes
An error occurred while saving the comment Geoffrey commented
Hi Salman,
Sorry, I hadn't seen your question.
We have opened a ticket regarding this issue already. See https://support.mongodb.com/case/01056829
In fact, an example scenario.
An X system's IT team creates and manages X.509 certificates for application authentication.
Security Team issues root certificates and intermediate certificates.
In the situation that the Security team detects that a certificate is compromised, this team could decide to revoke the intermediate certificate to avoid any data leakage. This team does not have access to the MongoDB Atlas portal because they do not manage the databases. As a result of this action, it is expected that all X.509 certificates issued under this authority chain will be unable to connect to MongoDB clusters.
Geoffrey shared this idea ·
-
29 votes
Geoffrey supported this idea ·
-
8 votes
Geoffrey supported this idea ·
-
14 votes
Geoffrey supported this idea ·
-
3 votes
Geoffrey supported this idea ·
-
3 votes
Geoffrey supported this idea ·
-
3 votes
Geoffrey supported this idea ·
-
3 votes
An error occurred while saving the comment Geoffrey commented
It can be very usefull if the database user can be automaticaly disable after x unsuccessfully login try.
Geoffrey supported this idea ·
-
90 votes
Geoffrey supported this idea ·
-
2 votes
Geoffrey supported this idea ·
-
8 votes
Geoffrey supported this idea ·
-
2 votes
Geoffrey supported this idea ·
-
3 votes
Geoffrey supported this idea ·
-
2 votes
Geoffrey supported this idea ·
-
1 vote
Geoffrey supported this idea ·
-
13 votes
Geoffrey supported this idea ·
-
6 votes
Geoffrey supported this idea ·
-
2 votes
Geoffrey supported this idea ·
Bonjour MongoDB,
We again had a problem with encryption at rest on one of our MongoDB Atlas clusters. After a rotation of the secret for access to the encryption keys, one of the nodes of a recluster did not go up. No alerts available in MongoDB Atlas to monitor this are available. We don't even have an event that indicates this problem to us.
We receive an email (which is not a good reliable monitoring method for us) from MongoDB informing us of the problem (ISSUE REFERENCE: PROACTIVE-57330).
We opened a support ticket after reading this message 24 days after receiving it. You must be able to monitor this type of incident via alerting in order to capture this type of problem as early as possible and avoid a production incident.
See our ticket for this occurrence of the problem.
https://support.mongodb.com/case/01222635