Ops Tools
221 results found
-
Add an option to GUI to rotate Certificates
Add an option to GUI to rotate Certificates for each or all instances of replicaset for MongoDB.
Should include options:
1) rotate certificates for one instances on one server.
2) rotate certificates for all instances belonging to a replicaset.
3) rotate certificates for all instances on one server.
4) rotate certificates for all instances on all servers for a project.3 votes -
Supporting the installation of mongosh in Ops Manager Local Mode
Ops Manager v6.0+ supports installing the new mongo shell (mongosh) to the deployment nodes. This feature is not supported in Ops Manager Local Mode.
It would be convenient to the Ops Manager Automation user if they could upload the mongosh binary to the Ops Manager Versions Directory and Ops Manager will install the binary to the deployment nodes similar to the MongoDB Binary and MongoDB Database Tools.
Currently, the customer with Local Mode needs to manage the installation of mongosh outside of Ops Manager Automation.
4 votes -
Send activity feed event by email similar to Alerts
We need to be informed and or react on some activity feed events. So we want to either be able to configure alert on specific activity type and/or be able to push activity feeds somewhere similar to alerts. then we would be able to configure actions based on activity type.
4 votes -
clear text password for mongodb ldap authorization
Add the feature to Encrypt the queryPassword parameter for LDAP in the config file directly via Ops Manager , so that text password should not be present in config file.
Keeping direct password is a security concern.
Sample format of the config file:ldap:
authz:
queryTemplate: '{USER}?memberOf?base'
bind:
method: simple
queryPassword: <Password>
queryUser: <username>
servers: serevername:port
transportSecurity: tls
userToDNMapping: '[ { match : "xxxxx)))"
} ]3 votes -
Ops Manager: API endpoint for /databases should not require host
Currently the Ops Manager API to list databases requires a hostname: /groups/{PROJECT-ID}/hosts/{HOST-ID}/databases
It would useful to gather databases on a project or cluster level instead as the databases are the same across replica set members.
1 vote -
custom defined roles In OPS Manager
We need a custom defined role to perform specific functions in the OPS Manager.
For Example --> We need a custom defined role which can perform subset of functions from Project Automation Admin Role + Project Read Only Role + rs.stepDown() functionality
Project Automation Admin Role:
View deployments.
Provision machines.
Edit configuration files.
Download the MongoDB Agent.
+ Project Read Only role.Project Read Only Role:
Activity
Operational data
Ops Manager Users
Ops Manager User roles.** This feature becomes very useful to contain the access of certain privileges and to have the flexibility tailormade privileges instead of giving the…
5 votes -
Add a cross reference of all projects and roles to user profile
I must click on projects to display all the projects in my list, click the Users link for a project, then search for my ID to see the roles assigned to my ID.
My idea is to consolidate this information and display it under my user profile similar to the Organization page. 3 clicks display my roles for each project on a single page.
1 vote -
add organisation name to project name when project name is not unique
There are multiple places where we need choose project. for example, to create global alerts we can exclude some projects from this alert.
The issue is project name is not unique and there could be projects with the same name in different organisations. For example, every organisation may have project dev or test.
it comes to the issue that you will see in the list of projects "dev,dev,dev,dev" and you don't understand which one you want to use.
it will be much better to display them in the format "org/project", so the example above would be "org1/dev, org2/dev, org3/dev" which…
1 vote -
Build Ops Manager packages for ARM architecture
The new Graviton instance types in AWS seem very promising from a cost/peformance perspective. We would love to be able to run our Ops Manager cluster on these new instance types, but there currently aren't any packages available for ARM architectures!
5 votes -
Add flexibility to disable and enable specific fetures of managing mongodb instance in OPS Manager (like user Sync)
Currently , Mongodb admin can not select to disable or enable feature after put mongodb manageed under OPS Manager. like security control .
Normally , Security control is not mongodb or Ops manager admin's responsibility , which is managed by a enterprice access control team.
1 , In opsmanager , there is not role for security control, like useradmin in mongodb.
2 , When ACCESS control team create role in mongodb. Ops Manager sycn it back.
3 , Opsmanager admin have to be engaged to work with ACCESS control team to complete the task.It is kind of not least…
1 vote -
ops manager agent support for Rocky Linux
Ops manager and Mongodb work on Rocky, but it seems there is no option for Rocky in the Ops Manager agent manifest, the current agent detects no Linux flavor for Rocky Linux. This already works on RHEL/CentOS and Rocky is supposed to be fully compatible with these OS's.
4 votes -
Set log file permissions using Ops Manager
Currently there is no way to set the log file permissions from Ops Manager and the default value is 600. Our organization uses Splunk and with the current settings the Splunk user is not able to read the log files. Config file options such as processUmask and honorSystemUmask can be used to change the log file permissions, but they will also change other files such as journal files, wiredtiger files, etc. The only option we have is to add the Splunk user to our role group in Unix, but this causes a security issue.
1 vote -
“Content-Security-Policy” header
Hello,
We want to add the “Content-Security-Policy” header to the OpsManager/MongoDB answers to increase the security level:
frame-ancestors 'none' (Do not render in frames)
script-src 'self': only loads scripts originating on the site (subdomains excluded)
default-src 'none': recommended for services returning HTML.
Could you please tell us how to set up these elements ?Thank you in advance for your support.
Regards
7 votes -
OPS Manager should call updateUser to change password to trace it in DB Audit.
If you enable auditing in database, you can't trace change password actions. The reason is OPS Manager updates system.user collection record directly. as a result, this action is not traceble in audit if parameter auditAuthorizationSuccess is not enabled.
But enabling this parameter cause performance degradation as all DML/DDL will be sent through audit layer.
Dropping user at the same time happening as expected and traceable in audit files.
1 vote -
Agent authentication to opsmanager using x509 credentials
Similar to how Opsmanger can use x509 to manage deployments, it should be possible to configure the agents to use x509 credentials to communicate with Opsmanager. This will allow for a more consistent security posture across the whole mongodb/opsmanager stack. It would also simplify security procedures such as credential rotation by unifying the authentication mechanism.
This will be an alternative to the existing API Key approach https://www.mongodb.com/docs/ops-manager/current/tutorial/manage-agent-api-key/index.html
1 vote -
Ability to remove parameter tlsCertificateKeyFilePassword from Advanced configuration
Currently the behavior around this parameter is tricky -once you added this parameter to advanced config - you can't remove it. if you try to remove it - OPS Manager simply ignores this action and when you run "Review and Deploy" - it displays nothing but still let you deploy this "nothing". similar if you want to set the value of this parameter to empty string from something - OPS Manager ignores it and deploy empty list of actions.
the workaround is to remove both tlsCertificateKeyFile and tlsCertificateKeyFilePassword in advanced config, but don't deploy it. then add back tlsCertificateKeyFile parameter…
1 vote -
Ops Manager API should be authenticated via Certificate
Ops Manager API uses HTTP Digest Authentication, this method requires a username and a password which are hashed and provided in the form of registered Ops Manager account, and the password which is a Public API Key associated with that account.
But as part of security feature we should be allowed to use Authentication based on SSL certificates as we are using for Client connection, This will help to secure the self automation process if we are developing any internally.
3 votes -
When changing snapshot retention, prompt user to apply new policy to existing snapshots
Currently when you change the snapshot schedule, the changes only apply to NEW snapshots.
Please allow the user the option to apply the new policy automatically to all existing snapshots. Or at the very least, notify them of them of snapshots that exist which do not meet the current policy!
Let me provide an example of the problem. If you have a retention policy of 10 days and on DAY1 you change it to 30 days, your retention will look like this:
DAY1 - 10 snapshots
DAY2 - 10 snapshots
...
DAY10 - 10 snapshots
DAY11 - 11 snapshots
DAY12…1 vote -
Lock enableLocalConfigurationServer setting on OPS Manager side
To harden security for mongodb deployment managed by OPS Manager, we can use setting enableLocalConfigurationServer = true so automation-mongod.conf won't have any passwords for ssl certs and agent will retrieve them from OPS Manager.
to disable this feature and to read all passwords for ssl certs (and hence get access to mongodb data) it's enough to comment out this parameter an restart automation service (or wait until host will be restarted).
Linux root user can modify any file on mongodb host including this file and can restart any services, so it's impossible to protect getting all passwords and mongod.conf from…
1 vote -
I found what I believe to be an error in the following document
I found what I believe to be an error in the following document.
https://www.mongodb.com/docs/ops-manager/current/tutorial/install-simple-test-deployment/In the section "5. Create the Ops Manager Application Database directory," it instructs to execute the following command
sudo chown -R mongod:mongod /dataIn my environment, the mongod user does not exist and I get an error, but looking at the passwd file, the mongodb user and mongodb group seem to exist. The version is 11.7.
I think the correct command is as follows
sudo chown -R mongodb:mongodb /data1 vote
- Don't see your idea?