search

GitGuardian / gitguardian-vscode

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.
https://marketplace.visualstudio.com/items?itemName=gitguardian-secret-security.gitguardian
MIT License
21 stars 0 forks source link

Extension Doesn't Honor Proxy Cred Injection #37

Open rgajason opened 1 month ago

rgajason commented 1 month ago

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:

GITGUARDIAN_API_KEY=unset
GITGUARDIAN_INSTANCE=https://gg-api-auth.our.internal.domain

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.

mathieubellon commented 1 month ago

Hello @rgajason, I think we can update our design to suit your case - expect an update in the coming days

mathieubellon commented 2 weeks ago

Hello @rgajason Can you tell me if the recent v0.4.0 release help to solve your problem ? We just deployed it on the marketplace, I think you just need to upgrade the extension

rgajason commented 2 weeks ago

Hi @mathieubellon . I upgraded to 0.4.0 on VSCode 1.95.1 and it is still prompting me to authenitcate (to link my IDE with my account).

mathieubellon commented 2 weeks ago

Hi @rgajason - strange, I'll get back to you shortly

mathieubellon commented 4 days ago

Hi @rgajason ,

We released version 0.5.0 yesterday, which improves the authentication flow. The extension now natively handles environment variables. Based on your issue description, we believe that version 0.5.0 should work for you. However, please note that we couldn't test your specific proxy use case in a timely manner. If the issue persists, I will coordinate with your CSM to set up a call regarding this matter.