- Select User menu > Integrations from the left sidebar.
-
Click Manage next to Azure DevOps under Source Control Managers.
- Click the three vertical dots next to the integration. You can choose from the following options:
Update Credentials
To update the Azure DevOps App credentials:-
Click the three vertical dots next to the integration, and select Update Credentials.
You cannot update the host URL of an existing integration. To monitor a different organization, create a new integration.
- You can update your Personal Access Token.
- Click Save.
Initiate rescan manuallyCredential updates take effect at the next scheduled scan cycle. To apply changes immediately, select Rescan Org.
Edit Azure DevOps App integration
To edit the Azure DevOps App integration:- Click the three vertical dots next to the integration, and select Edit Configuration.
-
You can update your personal access token and choose the scanners.
-
Select Pull Request Settings to edit the PR scans configuration. See Azure DevOps App PR scans for more information.
Permissions for your credentialsEnsure that the credentials have the Code read and write access. See create an access token for more information.
-
Click Update Configuration to save the changes.
The changes are applied from the next scanning cycle.
Click Rescan Org after editing the integration to apply changes immediately instead of waiting for the next scheduled scan.
Delete Endor Labs Azure DevOps App
To delete an Azure DevOps App integration, click the three vertical dots next to the integration, and select Delete Integration. When you delete the integration, it will also delete all child namespaces, projects and references associated with the auto-generated root group namespace. It also deletes any manually created namespaces and projects under auto-generated namespace.View sync logs
Endor Labs detects and reports installation and synchronization errors during organization sync. These include expired tokens, insufficient permissions, invalid host configurations, and certificate issues. Sync logs report those errors that you can resolve. To view sync logs, click the three vertical dots next to the integration, and select View Sync Logs. The sync logs display details of synchronization attempts, including timestamps, error types, and diagnostic messages. These logs help identify issues such as authentication failures or configuration problems.Types of errors
The sync logs detect and display the following categories of sync failures:- Expired or invalid Personal Access Tokens (PATs): The PAT used for authentication has expired or is no longer valid. Edit the integration and provide a valid token.
- Insufficient PAT permissions: The PAT does not have the required scopes, such as repository read access. You must generate and provide a PAT with the correct access.
- Certificate related access issues: The certificates required to connect to the SCM are invalid, outdated, or untrusted. This error occurs in self-hosted GitLab instances that use custom SSL certificates. Update the certificate configuration or ensure the certificate chain is properly trusted to resolve the issue.
- Incorrect or invalid host URLs: The configured URL is incorrect or unreachable. Since you cannot edit the host URL, you need to delete and reinstall the integration using the correct URL.
