B
Benoit Martin
I'm developping a windows app that will be sold to different clients. The
app connects to a Database located on my server. That app is installed on
multiple machines for each client.
Each client will have his own database on my server. What would be the best
approach to keep the connection data secure and easily manageable? I don't
want to have the connection string or parameters in the app.config file. One
of my fears is also to give a version to a client with the connection string
for another client giving him access to the wrong DB.
I was thinking that one of the easiest way might be to have their sys admin
enter that info during installation and to store it encrypted in a text
file. Is it a good solution?
How would you go about that?
Thanks
B
app connects to a Database located on my server. That app is installed on
multiple machines for each client.
Each client will have his own database on my server. What would be the best
approach to keep the connection data secure and easily manageable? I don't
want to have the connection string or parameters in the app.config file. One
of my fears is also to give a version to a client with the connection string
for another client giving him access to the wrong DB.
I was thinking that one of the easiest way might be to have their sys admin
enter that info during installation and to store it encrypted in a text
file. Is it a good solution?
How would you go about that?
Thanks
B