Skip to main content

Hi everyone - hoping to get some help with an issue we ran into yesterday.
We have a HUB connection to Azure Dev Ops (ADO) using a Personal Access Token which expired over the weekend.  When we renewed the token, the ‘Test Connection’ works fine and appears green, however the collections/integrations using that repository are now throwing an error about the ‘Collection Credentials’

Connection credentials were not accepted by the repository. Authentication credentials were not accepted by the server: ensure the correct form of authentication is enabled on the server and that the Domain is specified if applicable.

Other than the PAT nothing changed on the repository. 

Is there something missing on the collection that I need to reset the link to the repository?

 

 

​@ShaneDodge , 

 

When a  PAT for an Azure DevOps (ADO) HUB connection is renewed, the repository "Test Connection" may work, but collections and integrations might still fail with a "Collection Credentials" error about authentication, even though nothing else changed on the repository.

Here are the key check points - 

  • Re-check that the PAT was generated with the correct scope and for the correct user. 
  • PAT should have: READ access for Projects, Teams, and Identity, READ/WRITE access for Work Items (and Test Items, if used)
  • Be sure the new PAT is updated in the repository connection configuration within Hub.

If all validation steps pass but the error persists, Please raise a customer care case with detailed configuration information

Terms of UseCookie settingsAccessibility statement
All Data Subject Access Requests (DSARs), and requests of “Do Not Sell My Personal Information” according to the CCPA, must be submitted through the Planview DSAR portal located here

Planview has appointed a Data Privacy Officer (DPO) to be responsible for overseeing our Privacy Management Program and related privacy compliance measures. DPO can be contacted at privacy@planview.com