- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-19-2024 03:07 AM
Hi All,
We are trying to setup integration between Infoblox and ServiceNow using the Service graph connector but that is not working.
we are getting below error which means ServiceNow is not able to connect to infoblox URL itself
Unable to make a connection to Infoblox API call. Please check your credential configuration. Check system log for more details. HTTP return status code was -1
Has anyone been able to solve this error.
Went through the below link but not able to find the network flow attribute itself.
Thanks,
Rohan Bathla
Solved! Go to Solution.
- Labels:
-
Service Graph Connector
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2024 11:43 PM
Hi All,
We were able to solve this issue with the help from ServiceNow support.
On the mid server host that we were using for connecting the ServiceNow instance to infoblox we had to perform below steps.
The recommended approach would be to work with the endpoint team to to remove the unwanted certificates from the certificate chain in order to avoid this issue in future.
2. However there is a solution that can be adopted changing two Java additional properties in the MID Server:
i. Stop the MID server
ii. Open file \agent\conf\wrapper-override.conf
iii. Add these two parameters:
-Djdk.tls.maxHandshakeMessageSize=49152
-Djdk.tls.maxCertificateChainLength=40
iv. Start the MID server
v. Test the REST Message and the issue should be resolved.
The -Djdk.tls.maxHandshakeMessageSize increase the HandshakeMessage size and the -Djdk.tls.maxCertificateChainLength increase the maximum allowed length.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-22-2024 08:10 AM
Hi @Rohan31 ,
Refer below articles, which may help you.
https://www.servicenow.com/community/in-other-news/service-graph-connector-for-infoblox/ba-p/2438968
Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.
Thanks
AJ
Linkedin Profile:- https://www.linkedin.com/in/ajay-kumar-66a91385/
ServiceNow Community Rising Star 2024
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-23-2024 12:58 AM
Hi Ajay,
Thanks for replying but I have already been through these links while setting up the SG connector for infoblox.
Appreciate you trying to help though.
Thanks,
Rohan Bathla
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-23-2024 12:56 AM
Hi Ajay,
Thanks, but I have already been through these links to setup the SG Connector for infoblox.
But I appreciate you trying to help.
Thanks,
Rohan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2024 11:43 PM
Hi All,
We were able to solve this issue with the help from ServiceNow support.
On the mid server host that we were using for connecting the ServiceNow instance to infoblox we had to perform below steps.
The recommended approach would be to work with the endpoint team to to remove the unwanted certificates from the certificate chain in order to avoid this issue in future.
2. However there is a solution that can be adopted changing two Java additional properties in the MID Server:
i. Stop the MID server
ii. Open file \agent\conf\wrapper-override.conf
iii. Add these two parameters:
-Djdk.tls.maxHandshakeMessageSize=49152
-Djdk.tls.maxCertificateChainLength=40
iv. Start the MID server
v. Test the REST Message and the issue should be resolved.
The -Djdk.tls.maxHandshakeMessageSize increase the HandshakeMessage size and the -Djdk.tls.maxCertificateChainLength increase the maximum allowed length.