Security concern for license approach for .Net Core 2.2

[nicoleta.scrimint]

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!

[Shalex]

Please refer to https://www.devart.com/dotconnect/oracl ... ndard.html:

You don't need to specify your license key in every connection string. Once a connection with a valid License Key is successfully opened, there will be no further license check in a current application domain. So, you can load your license key from somewhere (from embedded resource, etc.), open a test connection, and after this your application can work with connection strings without License Key.