- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-30-2020 06:51 PM
I need a big help on this integration since the log is not enough to troubleshooting. How do I collect detailed log or maybe do steps to make sure what's the part of integration is getting any trouble. I have done the same steps in the Postman and everything is working good, Servicenow requires different mechanism?
Solved! Go to Solution.
- Labels:
-
Service Catalog
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-02-2020 11:17 AM
Folks, case was solved this morning!
I engaged Ansible team and also network team from customer side. The issue was in the Firewall rule that's why the connection was getting refused. I appreciate a lot for all insights and value comments in this post!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-30-2020 07:52 PM
Well you can log the payload which you are sending or receiving. If you could describe the integration which you are trying to achieve may be you will get better answer.
This might help you in improving logging functionality https://github.com/tbrosow/SNOW-Logger
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-01-2020 02:18 AM
hi Aksras,
This is an integration with Ansible Tower, I have followed this documentation below:
https://www.ansible.com/blog/ansible-servicenow-howto-part-3-making-outbound-restful-api-calls-to-ansible-tower
As I said, the steps were done in Servicenow and Postman, but only from Servicenow it logs me the error 403, that's why I have requested support to troubleshooting this kind of issue.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-01-2020 02:37 AM
Thanks Antonio, that document helped in understanding what you are doing. It seems you need to do client authentication by passing the certificate which POSTMAN could do flawless. In servicenow Client Authentication is done a bit differently. Now its worth trying so I will share the steps:
1. Create a Protocol Profile System Security->Protocol Profile something like this and select the certificate record you have added:
2. Go to your REST message record where you are testing, select USe Mutual Authentication as shown below screenshot before clicking TEST
Try this bit as well, if doesnt work we will investigate further.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-01-2020 03:11 AM
Appreciate your quick response!
I have include the certificate in that way you have mentioned, it is not working yet. I received 2 certificate files, .cert and .key, when I tried .key appears a message saying the format is not support, I tried all of option there. Then I have used .cert and the same error occurred.