Hey all....
I'm catching a few problems where after an instance has moved over to our new state of the art Data Center that the Mid Server no longer functions and reports as 'down' in the instance. In checking ~/agent/logs you would see that there are lines of errors stating "could not connect to instance bad username/password".
What's happening that in conjunction with your move we are enabling basic authentication on your instance enhancing the logical security of your deployment. Do know this is effecting only our legacy discovery customers only who do not have the authentication piece enabled prior to the move.
Our current install process has been updated to include this requirement but if you have not moved over yet or are scheduled to, you can do a couple things to prepare your side so everything works the moment after the migration.
-In the ~/agent/config.xml file edit the server URL to reflect your Fully qualified Domain Name (FQDN).
-Create a custom user in your instance for the MidServer to connect with.
-Enter those credentials in the config.xml file under mid.instance.username and mid.instance.password values.
-Remove the discovery upgrade branch value if you have one entered.
-Save the config.xml
-Restart the MidServer
Below is what a completed mid-server config.xml would look like. You can make these changes today with no impact or after your move whichever suits your process best.
