Security concern for license approach for .Net Core 2.2
Posted: Tue 19 Feb 2019 07:55
Hi,
In the following article,
https://www.devart.com/dotconnect/oracl ... ndard.html
it is specified that it is needed to include the Devart account activation key in the connection string.
We store the connection string in the appsettings.json configuration file for the .Net Core 2.2 application.
Is this activation key be a security concern, if it is provided to customers, when the application is installed on the customer machine?
We will encrypt the connection string in the appsettings.json.
Thank you!
In the following article,
https://www.devart.com/dotconnect/oracl ... ndard.html
it is specified that it is needed to include the Devart account activation key in the connection string.
We store the connection string in the appsettings.json configuration file for the .Net Core 2.2 application.
Is this activation key be a security concern, if it is provided to customers, when the application is installed on the customer machine?
We will encrypt the connection string in the appsettings.json.
Thank you!