-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Token-based authentication is broken #19
Comments
I think I've encountered the same issue. I notice that if I leave out my password and try using the token based auth, I get this VS Code error message:
I figured it was an empty setting and, it seems, it is. So somehow the code is trying to access the password field, and it's empty, so it's "undefined or null", but should be a string. |
I've found if i put my token in for the password it works. i tried this after noticing a lot of plugins mention using tokens in their password fields, or call the field password_or_token though this is pretty confusing. i think the token param should be removed and the docs updated to say to put the token in the password field |
Interesting point.. I took a look into my configuration (using token) and i have written my token value into |
Would be fixed by #31 |
VS Code 1.40.2
Jenkins Pipeline Linter Connector 1.2.0
After a quick look into the source, this line seems to be the issue:
https://github.com/janjoerke/vscode-jenkins-pipeline-linter-connector/blob/master/src/extension.ts#L63
The variable
options
doesn't have a propertyheaders
...The text was updated successfully, but these errors were encountered: