Using REST API Explorer | new role required "web_service_admin" !?

[Meloper]

UPDATE: 

I saw there is already a Problem: PRB1744904

----

Hi,

in the Past, Users were able to use the REST Api Explorer with "rest_api_explorer" role.

Since Nov 2023, there is a new ootb ACL.
name: Doc Service API

Which also needs the Role: "web_service_admin".

This new role give access to: read, create, modify, and delete Scripted REST APIs and web service resources.
https://www.servicenow.com/community/now-platform-forum/what-does-the-role-web-service-admin-give-to...

Of course i dont want that!

But without the new role you can access the API Explorer via the navigation but the drop downs are empty due to missing rights (new role)....

Any ideas.
In the best case i dont want do change ootb ACL or add new but in this case...

[Meloper]

I saw there is already a Problem: PRB1744904

[Brian Scott2]

Looks like they added a new ACL (in our case, with a security patch in Vancouver).

Here's the ACL in our Vancouver instance and I verified it is the same ACL in a Washington DC developer instance;

https://[environment].service-now.com/nav_to.do?uri=sys_security_acl.do?sys_id=88c55a714332311076eca0246bb8f283

Here's the query to find it if it happens to have a different sys_id in your environment;

https://[environment].service-now.com/sys_security_acl_list.do?sysparm_query=name%3DDoc%20Service%20API%5Eoperation%3Dexecute

I just added the rest_api_explorer role along side the web_service_admin role and its working for our users now.