JGarza214146 (Community Member) asked a question.
Hi, just installed latest version of Veracode Extension for VSCode. I configured my credentials file and I can see the credentials are picked up in the extension log in VSCode. However on startup I'm getting an html error page in your log (see below). It looks the extension is making a HTTP call to an external website? Or maybe to the wrong address? The log doesn't indicate what address is being attempted.
Question 1: Is there a way to increase the verbosity of the log to determine what web address it is attempting to connect?
Question 2: Are there any other configuration parameters available to the extension that would allow us to enter a correct url? Other than the ones listed here:
https://help.veracode.com/reader/eAvornYxfrGF2caDJIBu_g/cfJfhh0dvy_nl_GB3M2aYQ
Here is the log:
[4:58:01 PM] - info - Credentials file: C:\Users\james.t.garza\.veracode\credentials
[4:58:01 PM] - info - Using credentials default profile.
[4:58:01 PM] - error - <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Password Expired</title>
<link href="https://sweb.traderz.com/proxy_block/css/proxybase.css" rel="stylesheet" type="text/css">
</head>
<body>
<div class="container">
<div class="header"><img src="https://sweb.traderz.com/proxy_block/images/traderzLogo.gif" width="80" height="80" alt="Charles traderz" /></div>
<div class="sidebar1"> </div>
<div class="content">
<h1><img src="https://sweb.traderz.com/proxy_block/images/icon-warn.gif" width="28" height="27" alt="Warning icon" /> <span class="title1"><FONT COLOR=#f9ad17>Your Password has expired</FONT></span></h1>
<p>Your windows login "<strong><!--END SITE VALUE--></strong>" password has expired and is required to access all external websites. <br>Please change your password now. Once updated you will be allowed acces to the internet.
<br><br>Change your login password using one of these methods:<br><br><ol><li>Log off and log back on to your workstation then update your password when prompted</li><li>Go to <a href=https://password.traderz.com>ePass</a> https://password.traderz.com / jumpword: <i>ePass</i> and follow the steps to change your password</li> <li>Call the DSD at 888-PIC-SITE</li></ol><br>
If this issue persists please feel free to contact the proxy services team at <a href=mailto:websitereview@exchange.traderz.com?Subject=Internet%20Access:%20%20Password%20Expired%20question%20from:%20&body=Attention%20proxy%20team%0AI%20received%20the%20following%20message%20Password%20Expired%20when%20attempting%20to%20access%20the%20website%20api.veracode.com:443.%0APlease%20help.%0AThank%20you.>websitereview@exchange.traderz.com</a></p>
</div>
</body>
</html>
.png){kind=logo}
Hi @JGarza214146 (Community Member) , thank you for your question! I will forward it to the @Integrations Group for visibility.
Any movement on this? How long should I expect to be waiting on support?
I did a bit more digging, it looks like the error page is coming from my corporate proxy. On windows, I was able to add the proxy information to the user settings as so:
"http.proxy": "http://proxy.traderz.com:8080",
"http.proxyAuthorization": "Basic abzyJOjkoJEKO..."
This has resolved the issue under windows. However, I also need to get this working under Mac OS. Duplicating the same information on my mac does not resolve the issue. I've restarted VSCode and also logged out and back into my user account under MacOS. Any other things to try?
I ended up getting this working under MacOS. For whatever reason the http.proxyAuthorization steps (listed above) work on Windows but not on MacOS. I ended up using the cleartext approach for the proxy configuration as follows:
This works on both Mac and Windows.
Hope that that's the problem.
P.S. Make sure to authenticate the API account with ID and Key rather than username password.
See my response for getting this working on the Mac. The proxy credentials are specific to VSCode and not your extensions, so until VSCode resolves, the clear text approach will have to suffice.
I am aware of that was the Proxy authentication. It was only a P.S. courtesy note.