Skip to Main Content

MongoByte MongoDB Logo

Welcome to the new MongoDB Feedback Portal!

{Improvement: "Your idea"}
We’ve upgraded our system to better capture and act on your feedback.
Your feedback is meaningful and helps us build better products.

Status Submitted
Categories Under Review
Created by Guest
Created on Oct 9, 2020

Automation web UI - Validate the TLS/SSL settings passed in the UI

It is possible to make all agents in a project fail by setting a wrong CA file value. For example a customer set in the CA file field a directory instead of a file, and it caused Agents to stop reporting to OM. Eg. the montioring module logged: {code} Error starting new module : [15:25:38.817] Error starting Monitoring module : error parsing settings: `map[logFile:/var/log/mongodb-mms-automation/monitoring-agent.log maxLogFileDurationHrs:24 maxLogFileSizeBytes:1048576000 maxProcs:0 mmsApiKey:*** mmsBaseUrl:https://api-agents.mongodb.com mmsGroupId:yyyy sslTrustedServerCertificates:/opt/mongodb/db1/pki version:10.19.2.6597]`. Monitoring unable to start. Error: SSL trusted server certificates file `/etc/ssl/pki` can not be read. Err: read /etc/ssl/pki: is a directory {code} Similar errors are likely present in the Automation and Backup modules logs. It would be nice if the UI validates what's entered in the web UI.