- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-28-2017 11:50 PM
Hello,
I have created a REST Web service to record data in tables in servicenow.And I am calling this web service from an external client.
But sometimes whenever I call the web service,it gives me "Error 404:requested resource is not found" in response and when I refresh the page or send the request from client again,it executes and web service starts to work normally.
When I checked about this reponse,so I found a term ACL constraint.What effect does it implies.As I am already using ACL authorization on my web services.
Please help me out,how can I overcome this problem so that my web service works smoothly.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-29-2017 05:19 AM
Hi Ishaan,
I don't think it is something to do with the timeout issue.
Can you check the configuration done to consume the servicenow api in the third party application.
What do you mean restarting and then working fine?
What do you restart? Is it the client application which consumes the API or ServiceNow instance refresh.
if you are saying that you need to restart the client application in order to remove that error then it is something to do with the third party application and not with ServiceNow.
If every time you are getting correct response from servicenow api endpoint from Postman tool then there is no issue with ServiceNow.
Mark Correct if this solves your issue and also hit Like and Helpful if you find my response worthy based on the impact.
Thanks
Ankur
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-28-2017 11:53 PM
Hi Ishann,
Are you using the correct end point in the third party application.
Usually ACL box should not be check since you must be consuming the end point with some API user usually with certain roles such as rest_explorer etc.
Mark Correct if this solves your issue and also hit Like and Helpful if you find my response worthy based on the impact.
Thanks
Ankur
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-29-2017 12:20 AM
Yes,I am using the correct end point.It doesn't show that error everytime.Sometimes web service works fine and sometimes it returns "Error 404" as a response.And when I send the request again or when I refresh the instance the web service is called perfectly.
If I don't check the ACL box then how will I check for the user if it has the role to call the web service or not because I want only some users can call the webservice?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-29-2017 12:23 AM
Hi Ishaan,
You must have given a particular username and password to third party using which they will call the API. So only this user should call the API and this user will be present in ServiceNow user table
That is how it should be
Mark Correct if this solves your issue and also hit Like and Helpful if you find my response worthy based on the impact.
Thanks
Ankur
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-29-2017 12:41 AM
Hi Ankur,
Yes I have also done it in the same way.I have created a user and provided it the role for ACL authorization and provided the username and password to the third party.
But I am not getting the reason of Error 404.