TBenn080551 (Community Member) asked a question.

Azure Devops Pipeline Veracode plugin throwing "The profile 'default' does not exist" error

I checked and the API user credentials are correct and not expired (just updated them yesterday), the credentials and pipeline is connected to an Azure Service Connection and has been tested. Veracode app profile name is correct and matches. Any thoughts on what this could be? Error is below:

 

[2026.01.06 18:05:23.366] The profile 'default' does not exist.

Error occurred while accessing the Veracode Platform.

Verify that:

 

1.The login credentials are correct

 

2.The account is an API account with the necessary permissions.

 

3.The account is not locked.

 

4.The IP address of the Internet-facing machine is not restricted.

 

5.The VSO agent has the necessary permissions.

 

6.The port that the VSO agent uses is not restricted.

 

 


  • SamHouston (Veracode)

    Hi @TBenn080551 (Community Member)​ -

     

    Analysis Steps:

    1. Check that the Veracode account user profile, namely the API Roles and the ID and Key, are valid
    1. Check that IP whitelisting is done and the network does not need a proxy setup 
    1. Check the ADO configuration for the Veracode Plugin, Service Connection and Agent configuration
    2. Check if the ADO variables are correctly configured (name-wise), in case of use of "Credentials"

     

    Troubleshooting Steps:

    1. Create a New pipeline with new service connection and new environment variables and re-test.
    2. Try changing the agent for the pipeline to a new agent.
    3. Try changing the Connection Detail in pipeline from "Service Connection" to "Credentials" and vice-versa.

     

     

    If this does not resolve the issue, please contact us at: https://community.veracode.com/s/contact-support

     

    Expand Post
    Selected as Best
  • SamHouston (Veracode)

    Hi @TBenn080551 (Community Member)​ -

     

    Analysis Steps:

    1. Check that the Veracode account user profile, namely the API Roles and the ID and Key, are valid
    1. Check that IP whitelisting is done and the network does not need a proxy setup 
    1. Check the ADO configuration for the Veracode Plugin, Service Connection and Agent configuration
    2. Check if the ADO variables are correctly configured (name-wise), in case of use of "Credentials"

     

    Troubleshooting Steps:

    1. Create a New pipeline with new service connection and new environment variables and re-test.
    2. Try changing the agent for the pipeline to a new agent.
    3. Try changing the Connection Detail in pipeline from "Service Connection" to "Credentials" and vice-versa.

     

     

    If this does not resolve the issue, please contact us at: https://community.veracode.com/s/contact-support

     

    Expand Post
    Selected as Best
  • RHedin588584 (Community Member)

    Hello!

    Were you able to resolve this issue? If so, how did you fix it?

    We are running into the same problem.

    Thanks!

Topics (5)

No articles found
Loading

Ask the Community

Get answers, share a use case, discuss your favorite features, or get input from the community.