I use an MS SQL Server connection on my website.
For greater security my client would not want the connection data in App_Data\ServerConnect\modules \Connections\filename.json to be readable because the pages are located on an IIS of a potentially reachable location from outside
I thought of two possibilities, but I can’t handle either:
-Use a DSN system connection on that Windows (but I don’t know how Wappler can interface with that type of connection)
-Ensure that the JSON file has encrypted data in it. I tried to tick the entry “Encrypt” in Database Connection, but then I have this error when I do the test and don’t know how to fix it.
It would appear that the $_ENV.user definition is not set properly and hence is not being resolved to the user name.
Check your settings screen, ensure the settings are input for the correct target and ensure the ENV variables are set in the WordFlows/Globals
I followed the instructions step by step and did all the tests.
It’s true that the test doesn’t work, but neither does the app.
However I do not think it is the right way for my case: with this procedure the password information would still be visible in config.json
My project will run on an Internet Information Server (in localhost) of a pc, and then shared for access from the outside, protected by a firewall.
The customer is afraid that the login and password information can be discovered and the PC is vulnerable. If possible I would like at least the password information to be encrypted somehow
@Hyperbytes
the customer is paranoid because on that pc there is also a connection to a network disk where there are other company data potentially at risk in case of hacking
If placing settings in a json file was a security risk then the entire node server platform would be useless. Only files in the public directory are accessible directly.