Repeat the commands for the GlobalForms database.To do this, replace "use WorkflowEngine" with "use ServiceEngine", etc. Repeat the previous step for the ServiceEngine, PortalSecurity, and CaptureWorkflow databases.Open a Mongo shell by running the following commands from an Administrative Command prompt: It is case-sensitive, so "portalsecurity" is not the same as "PortalSecurity". You could also create the database using your querying utility.This creates the PortalSecurity database if it does not already exist. The simplest way to do this is to create a new Portal Connection and remove/secure a workflow to it.If you do not have a PortalSecurity database, create one.This database will only be present if you are using this MongoDB instance for GlobalForms 10.You are more likely to have this database if you upgraded from an earlier version. This database may or may not be present.Connect to your MongoDB instance using a Mongo query utility, such as Robo 3T.The next step is to configure the MongoDB users that we use to connect Ensure the names of your databases Using the username "globalforms10" and the password "globalforms10" This is done by adding "?authMechanism=DEFAULT" to the end of the URL. You also need to specify the auth mechanism. Add the encoded username and password to the URL.The URL entry should look something like "mongodb://:27017/GlobalForms". The exact file path may be different if you installed to a different directory. Navigate to the file "C:\GlobalForms\config\default.json".Note the encoded username and password.Encode your username and password (separately) using a URL encoder, such as this one:.It does not need to be an existing Windows user. To enable authentication, you must include the username/password in the MongoDB URL. GlobalForms 10 connects to MongoDB differently than GlobalSearch/GlobalCapture. You will need to edit this particular file for each GlobalCapture engine installed across your network C:\GetSmart\CaptureServices\GlobalCapture_1\.You will need to edit this particular file for each GlobalAction engine installed across your network C:\GetSmart\ or C:\GetSmart\ActionServices\GlobalAction_1\ depending on GlobalAction version.C:\inetpub\wwwroot\Square9Rest\web.config.C:\inetpub\wwwroot\Square9CaptureAPI\web.config.C:\inetpub\wwwroot\Square9API\web.config.To configure the Square 9 software, add the following entry to the "appSettings" section of the configuration files listed below.Ĭonfiguration Files (please note that the exact file path may vary on a non-default setup): If using Robo 3T (formerly Robomongo), you must use version 0.9 or higher to connect after configuring Mongo authentication in this manner.You can verify your version of MongoDB by navigating to "C:\GetSmart\mongodb\bin", right-clicking "mongod.exe", selecting "Properties", and viewing the "Details" tab.
An uninstall re-install will not upgrade to 4.2.
Only new installs of GlobalCapture 2.4 on servers that have never had an old install will install mongo 4.2.
GlobalSearch must be version 4.5.2.0 or later.The following requirements must be met prior to beginning this process: It is also recommended that all configuration files mentioned in this guide are backed up prior to being edited. Please read through the entire procedure before beginning. These steps listed below should be performed by an IT specialist or technical user, as improperly following these steps may accidentally lock you out of GlobalSearch/GlobalCapture.
The steps below detail how to to set this up.
However, this will restrict access to Square 9 software that needs to connect to MongoDB. MongoDB can be configured to require authentication for added security.