Configure the application settings

By default the staging service will attempt a connection to the default instance on the local machine ".\". If you are unable to connect to the SQL instance in this way, the configuration can be modified through the steps below.

1. Open the appsettings.json configuration file in a text editor:

   <InstallDrive>\Staging\<StagingServiceBuild>\Release\appsettings.json

2. Locate and modify the following entry, replacing Data Source=.\\ with the appropriate host\instance.

   "StagingContext": "Data Source=.\\;Initial Catalog=Staging;Integrated Security=True",

3. In the Serilog section, locate the path entry and change it to reflect the logging folder you created in Configure basic permissions.

   Please use \\ instead of \ in the logging folder path. For example, D:\\Logs\\StagingLogs\\log.log instead of D:\Logs\StagingLogs\log.log.

4. If using Windows authentication, locate the Authentication entry in the ApplicationSettings section, and change the value from AvevaConnect to Windows.

5. Locate the EnableCsrfCheck entry, which is set to true by default to prevent cross-site request forgery.

   If EnableCsrfCheck is set to true, non-AVEVA Staging clients sending HTTP requests to the Staging REST API must be modified to add a custom request header with key X-ClientType and value SDK. For example:

   httpClient.DefaultRequestHeaders.Add("X-ClientType", "SDK");

   Set the EnableCsrfCheck entry to false (not recommended) only if you cannot make this change to your custom code connecting to the Staging REST API.