MID Server Issues - ServiceNow REST Step Error for ADS Integration

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-24-2022 11:48 AM - edited 10-24-2022 11:52 AM
Hi Everyone,
I'm attempting to register some webhooks to connect ServiceNow and Azure Dev Ops and keep getting an error which I believe is related to MID Server configuration on my dev instance.
For context:
1. I am using the Microsoft Azure Devops Integration for Agile Development plugin
2. The way I am attempting to register said webhooks is by clicking a button available on a record called IT Project
The UI from which I am trying to register a webhook
3. The error is reported on execution records of a flow that is responsible for setting them up.
4. The errors are one of two, depending on how I've configured my HTTP(s) Connection for it
- In the first case, I configured it to select a specific MID Server and I got the error
- "Request not sent to uri= [Insert target URI] + java.net.UnknownHostException: tfsbeta.rockfin.com"
- In the second case, I configured it to auto-select a MID server and got the error:
- "Request not sent to uri= [Insert target URI] + org.apache.commons.httpclient.HttpException: Session contains no certificates - Untrusted"
What I need help with:
I only have the option to select either a specific MID Server or to auto-select one when configuring my http(s) connection record, and I'm at a loss for what to do in this situation since I am not an expert on this part of the platform. Any guidance on what to check for and if you're familiar with these errors would be very much appreciated.
- Labels:
-
flow designer
-
integration
-
Integrations
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-28-2022 07:49 AM
Hi Awae
I'm working as a pre-sales engineer with Exalate.
Exalate was designed with exactly these types of use-cases in mind, you could say that it is our "bread and butter".
One of Exalate's features, apart from syncing tickets bi-directionally, is the integration of Azure Devops and Servicenow.
Any entity will out-of-the-box be fully bi-directionally syncronized, which means, if a field gets updated on either side, it will automatically update on the other side, you can change this to make it uni-directional if you so please.
Cheers