DEsry124271 (Community Member) asked a question.
What's the path forward?
Ask the Community
Get answers, share a use case, discuss your favorite features, or get input from the community.
By clicking “Accept All Cookies”, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts.
.png){kind=logo}
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
Hi @DEsry124271 (Community Member)
To resolve this, you need to ensure that your API credentials are correctly configured. The extension requires your API credentials to be stored in a local credentials file.
For human user accounts, it is recommended to use Single Sign-On (SSO) with SP-initiated authentication instead of API credentials. With SSO, you can securely sign in to Veracode using OAuth from your IDE without needing to create or maintain an API credentials file (Create an API credentials file).
If you are using API credentials, please ensure they are generated in the Veracode Platform and stored in a local credentials file as described in the documentation (Create an API credentials file).
If you have recently added the Veracode Scan to Visual Studio, you might need to complete the authentication process again after ensuring your credentials are set up correctly. You can do this by selecting Open Veracode Scan from the toolbar, then navigating to the Getting Started tab and selecting your region, followed by Authenticate. If your API credentials are not automatically detected, you may need to manually ensure they are in the correct location and format.