Stop leaks. Safeguard your secrets with GitGuardian. GitGuardian actively prevents accidental exposure of sensitive information in your code, allowing you to code confidently and maintain the integrity of your data.
We have what may be considered an unsupported architecture, so feel free to close as such...
Our GGShield/GitGuardian users do not have accounts directly within the GG Dashboard. Instead, we inject the API authentication header using a proxy. When using the GGShield client directly our developer set two environment variables:
With these variables set users are not required to authenticate.
I've replicated this setup in the VSCode extension settings ("Api Url" and "Api Key") and restarted VSCode, but the extension is still prompting for login.
I've also tried to specify the GGShield path to my (Python package) installation of GGShield without change.
Environment
Describe the bug
We have what may be considered an unsupported architecture, so feel free to close as such...
Our GGShield/GitGuardian users do not have accounts directly within the GG Dashboard. Instead, we inject the API authentication header using a proxy. When using the GGShield client directly our developer set two environment variables:
With these variables set users are not required to authenticate.
I've replicated this setup in the VSCode extension settings ("Api Url" and "Api Key") and restarted VSCode, but the extension is still prompting for login.
I've also tried to specify the GGShield path to my (Python package) installation of GGShield without change.