Reputation: 467
I have written an Excel addin which connects to a specific database and pulls data from it. Currently, SQL Server authentication data is hard-coded in the add-in. I am planning to distribute the add-in without removing the SQL Server connection functionality. Protection of the authentication data is an inevitable prerequisite. However, I am stuggling to find a suitable solution.
The authentication data for SQL Server is not unique. Setting up a unique login for each end user would be nearly impossible.
Are there any recommendations how to best achieve a good protection level for the SQL Server authentication data?
Upvotes: 0
Views: 209
Reputation: 948
This is a very common problem of how to protect connection strings. Few years ago i have develop a C# application and i have used an app.config file that the connection strings to the db where encrypted.
Save the connection string in an external encrypted file and while reading it decrypt it:
You can check here for more information: https://msdn.microsoft.com/en-us/library/ms254494(v=vs.110).aspx
Upvotes: 1