Scripted Rest API user permisions

MehtaHarsh23
Mega Expert

Hi Team,

 

We have a scripted REST API to share our sctask and RITM details. We have setup a integration user for this. But integration user is not able to get any records in response. Response code is 200 but records in response is zero.

 

Which roles we need to give to user?

 

Observation: When we provide admin role it works. But when we try with specific role it does not work.

 

 

1 ACCEPTED SOLUTION

MehtaHarsh23
Mega Expert

We found the issue, Its related to our Data Segregation configuration, Its a business rule after disabling it use is able to get records.

We are still analysing the root cause, but its related to data segregation configuration.

 

Thank you all for your suggestions.

View solution in original post

9 REPLIES 9

Yes, Tried that also but issue was with data segregation configuration. Thank you.

@MehtaHarsh23 

 

Can you check Security configuration for your REST API

Bhuvan_0-1755693958995.png

Refer this section specifically,

Bhuvan_1-1755694183854.png

https://www.servicenow.com/docs/bundle/yokohama-api-reference/page/integrate/custom-web-services/con...

 

If this helped to answer your query, please accept the solution and close the thread.

 

Thanks,

Bhuvan

Ankur Bawiskar
Tera Patron
Tera Patron

@MehtaHarsh23 

If you are using GlideRecord in scripted REST API then it doesn't require any ACL.

If you are using GlideRecordSecure then ACLs come into picture.

If my response helped please mark it correct and close the thread so that it benefits future readers.

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

RaghavSh
Kilo Patron

Open your scripted REST API and check the value in Default ACLs?

Share the screenshot of scripted rest API.


Raghav
MVP 2023
LinkedIn

MehtaHarsh23
Mega Expert

We found the issue, Its related to our Data Segregation configuration, Its a business rule after disabling it use is able to get records.

We are still analysing the root cause, but its related to data segregation configuration.

 

Thank you all for your suggestions.