Why does an error occur when creating a DevOps Change Velocity tool, and how can I resolve it?

[kazuyamasud]

Hello everyone,

I'm encountering an error when trying to create a tool using the "Connect to a Tool" option in the DevOps Change Workspace within DevOps Change Velocity.

The error appears in the Permission Checks section, and I receive the following two messages:

- Part of the query on sys_certificate has been ignored because of insufficient access for 'query_match' operation on sys_certificate.type
- Part of the query on sys_certificate has been ignored because of insufficient access for 'query_match' operation on sys_certificate.active

I'm not sure if these errors are directly related, but I'm also experiencing an issue where the webhook auto-configuration does not display a list of repositories.

Could anyone advise on how to resolve this issue or suggest what I should check?

Thank you in advance!

[YaswanthKurre]

Hi @kazuyamasud ,

you’re seeing about sys_certificate indicates a permission/ACL issue in ServiceNow (specifically with query_match ACL's). Because Change Velocity tool onboarding uses certificate records (and other configuration records) behind the scenes, you need to ensure the integration user has the required rights to query/filter those records. Once permissions are corrected, the repository listing for the webhook auto-configuration is much more likely to succeed.

Also please refer this: https://www.servicenow.com/community/devops-forum/devops-insight-connection-permission-issues/m-p/25...

Mark this as helpful and correct, if this helps you.

Thanks,

Yaswanth

[kazuyamasud]

Hello @YaswanthKurre,
Thank you for your reply. It was very helpful and moved things forward.
The target environment does not allow me to change my own role because it is controlled by another administrator. However, I was able to assign the "admin" role to my test user through the administrator.

As a result, the previous error message disappeared, so it seems that permissions are indeed required.

That said, the repository list still does not appear even after adding the role. The issue where the repository search returns zero results remains unresolved.

I would appreciate any further suggestions or guidance on this.

Thank you again for your support.
Best regards.