Long shot, but crazy authentication issue

[mcascone]

I'm having a crazy issue, and nothing makes sense about it, so I'm reaching out here. It somehow seems sourced to running the linter.

I am running Jenkins on my local machine, and using VS Code to edit local files. I use the linter connected to the local Jenkins instance. I am testing with a jenkinsfile that does nothing but spit out echos.

And yet somehow, every time I run it connected to my company's VPN, a service account that I have never logged in to or have any affiliation with, gets locked out for bad user/pass, with a connection coming from my machine. We proved that it's my machine with the MAC address. The account will be fine, I'll run the linter, moments later it's locked from my machine's access. We repeated this several times. We searched literally everywhere on my machine that this account could be hiding, including the raw registry, turned up nothing.

I don't understand how this can be happening, but it is.

• everything is running locally
• Jenkinsfile does nothing but echo
• no external code is called
• i have never pulled down the repos that contain use of that service account

For what it's worth, the service account is SLP_DASH.

Is there any possible way this linter is somehow spitting out auth requests for random accounts on my domain?

Happy to provide any additional information.

Thanks.

[mcascone]

Well i found it: SLP_DASH is set as the Manager DN in the LDAP settings.

Why would the linter create a call out to the LDAP server, for a local connection?

[claydanford]

@mcascone, the extension is designed to connect to remote systems. Your use case is new and completely valid. It would be simple to add a check for localhost.