- Post History
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 07-19-2018 12:40 AM
Hello all,
I have had the opportunity to set up a lot of mid-servers lately. And i have found a helpful, yet vastly unknown "feature" with the setup via the installer. As most already know, mid-servers can be run through a defined proxy. Now when using the installer the user is required to provied a username and a password along with it. Same goes for the credentials for the plattform itself. But here is the difference:
After the installer is done, your instance password will have the following variable added to it:
<parameter encrypt="true" name="mid.instance.password" value="encrypted: ... "/>
Here the installer automatically adds the "encrypt" part to the password, preventing it from being readable within the configuration file. However it does not do this for the proxy password:
<parameter name="mid.proxy.password" value=" ... "/>
Therefore the proxy password can be read within the configuration file. This is easily fixed by just adding the variable to the parameter and restarting the mid-server. That then should look something like this:
<parameter encrypt="true" name="mid.proxy.password" value="encrypted: ... "/>
Greetings
Fabian
- 523 Views