Clarification on Event Delivery via MID Server for Custom Connectors
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Monday
Hi everyone,
I’d like to clarify the advantages of using a MID Server for event delivery in the context of a custom event connector—particularly when the delivery occurs over a corporate proxy in an outbound-only configuration.
As I understand it, sending events through a MID Server requires a MID Web Server component, which processes and forwards the events to the ServiceNow instance. In this setup, I assume the communication between the MID Server and the instance takes place via REST API. However, documentation on this specific flow is limited.
This leads me to question the actual benefits of using a MID Server in this scenario, especially when we have the opportunity to take a greenfield approach and avoid deploying MID Servers altogether. Are there any notable advantages in terms of:
- Security: For example, enhanced authentication mechanisms such as mTLS compared to OAuth?
- Delivery reliability: Is there a queuing mechanism or buffering capability that improves resilience compared to direct REST API calls?
Currently, the lack of detailed information about how the MID Server transmits events to the instance makes it seem like it may introduce unnecessary overhead without clear benefits.
I’d appreciate any insights or documentation that could help clarify this.
Reference: https://www.servicenow.com/docs/de-DE/bundle/zurich-it-operations-management/page/product/service-op...
