How does the authentication work for Push Connector using MID Server in Event Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-25-2025 03:31 AM
Hello all,
I am trying to configure a Push Connector via MID Server (using Event Listener). This is ServiceNow and third party integration and we have provided the API generated via "TransformEvents_MidJsonGeneric"
My query here is how we can authenticate as the 3rd party tool will be hitting the MID Server API URL (http://{MID_Server_IP}:{MID_Web_Server_Port}/api/mid/em/inbound_event?Transform={Transform_script}) and not ServiceNow. And they need authentication details to proceed further.
Please let me know how we can achieve authentication for this configurations.
Any quick help is much appreciated.
Thanks in advance.
Best Regards,
Pranita Bahuguni
- Labels:
-
Event Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-11-2025 09:04 PM
When using Push Connector via MID Server (Event Listener) in Event Management:
The authentication is handled via a shared secret token.
This token is configured in the Event Listener record in ServiceNow.
The third-party tool must include this token in the HTTP request as a custom header (e.g., mid.shared.secret).
Go to Event Listener record in ServiceNow.
Set the Shared Secret field.
Share this token securely with the third-party tool.
The third-party tool must send this secret in the HTTP header:
mid.shared.secret: <your_token>
MID Server validates the token before accepting the request.
No need for basic auth or OAuth in this setup — shared secret token is the method.
Please like if it is usefull.