Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

In some cases, it may be preferable to have MongoDB more secure than it is by default. While MongoDB isn't configured in our application to work with authentication, it can be locked down so that connections outside of the server are by default, rejected. Since all connections to Mongo are proxied directly through the Web Server, this will not interfere with users who are externally accessing GlobalCapture or GlobalAction.

Performing this action is fairly simple, as it requires only a very small modification of the Mongo Configuration file.

Step-by-step guide

  1. Stop Mongo DB service
  2. Open the mongod.cfg File (located in the Getsmart directory)
  3. Add the following line to the config file:
    1. bind_ip=127.0.0.1

  4. Save your configuration file
  5. Restart the Mongo DB service


Please Be Advised

This CANNOT be performed if your environment is running multiple GlobalCapture Servers or a stand-alone GlobalForms 10 server. This should ONLY be performed on a server where all GlobalCapture/GlobalSearch/GlobalForms applications reside



  • No labels