License Type | SaaS & On-Premise |
Agent Mode | Assess & Protect |
Main Product Category | .NET Agent |
Sub Category | Configuration |
Issue
Customers installing the .NET Framework Agent on a second drive letter might notice that their configuration is not being picked up by the agent.
Cause
Due to a regression in 20.7.3. the installer does not correctly set the permissions needed for creating log files or reading the YAML file.
Workaround
The following environment variable can be set to hard code where the agent looks for the contrast_security.yaml file.
CONTRAST_CONFIG_PATH
Example
CONTRAST_CONFIG_PATH=D:\contrast\dotnet\contrast_security.yaml
Resolution
A fix for this issue is currently in development. This work is tracked as SUP-1747.