# Elastic for ITSM - Servers can’t get passed proxy to our ServiceNow instance

**URL:** <https://discuss.elastic.co/t/elastic-for-itsm-servers-can-t-get-passed-proxy-to-our-servicenow-instance/360602>\
**Category:** Kibana\
**Tags:** elastic-stack-alerting\
**Created:** [May 31, 2024, 7:55am UTC](https://discuss.elastic.co/t/elastic-for-itsm-servers-can-t-get-passed-proxy-to-our-servicenow-instance/360602 "2024-05-31T07:55:54Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Naushad](https://avatars.discourse-cdn.com/v4/letter/n/eada6e/32.png) [@Naushad](https://discuss.elastic.co/u/Naushad)\
**Post date:** [May 31, 2024, 7:55am UTC](https://discuss.elastic.co/t/elastic-for-itsm-servers-can-t-get-passed-proxy-to-our-servicenow-instance/360602/1 "2024-05-31T07:55:54Z")

</div>

Hi all,

We are having an issue while connecting to ServiceNow Instance where MARS(elastic) servers can’t get passed proxy to our ServiceNow DEV instance which would need a path out.  
The current configuration does not have instructions to map mid server on this integration as elastic is located within DMZ and using OAuth for connection.  
Has anyone faced this issue?

Step to configure Integration

> **[ServiceNow ITSM connector and action | Kibana Guide \[8.13\] | Elastic](https://www.elastic.co/guide/en/kibana/current/servicenow-action-type.html)**