<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: PAM ServiceNow Ticketing integration in PAM Self-Hosted Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pam-servicenow-ticketing-integration/m-p/1409574#M84810</link>
    <description>&lt;P&gt;Thanks @Malhar Vora​&amp;nbsp; and @Sumit Kumar​&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 07 Oct 2025 06:08:24 GMT</pubDate>
    <dc:creator>Ferro</dc:creator>
    <dc:date>2025-10-07T06:08:24Z</dc:date>
    <item>
      <title>PAM ServiceNow Ticketing integration</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pam-servicenow-ticketing-integration/m-p/1409570#M84806</link>
      <description>&lt;P&gt;Hi all, &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I went through some of the documents with respect to SNOW integration and could not get info on the below&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1) To validate if the ‘Username’ validation can be updated to ‘Assigned to’ for CHG and INC, instead of ‘Requested by’ or ‘Caller’.&lt;/P&gt;&lt;P&gt;2) Online examples show the API call from CyberArk is using basic authentication.&amp;nbsp;&amp;nbsp;We cannot enable API access using basic auth without appropriate risks being raised and approved.&amp;nbsp; Is there any additional auth is permitted like OAUTH2 or Mutual Auth etc?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Documents referenced: &lt;/P&gt;&lt;P&gt;https://community.cyberark.com/s/article/CyberArk-Integration-with-ServiceNow-Ticketing-System&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A alt="https://url.au.m.mimecastprotect.com/s/Fto3CQnM8qH68wmz2HxfyuGQIlA?domain=docs.cyberark.com" href="https://url.au.m.mimecastprotect.com/s/Fto3CQnM8qH68wmz2HxfyuGQIlA?domain=docs.cyberark.com" target="_blank"&gt;&lt;B&gt;https://docs.cyberark.com/pam-self-hosted/latest/en/content/pasimp/ticketingintegrationservicenow.htm&lt;/B&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;B&gt;Regards,&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&lt;B&gt;Ferro&lt;/B&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Oct 2025 01:10:46 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pam-servicenow-ticketing-integration/m-p/1409570#M84806</guid>
      <dc:creator>Ferro</dc:creator>
      <dc:date>2025-10-07T01:10:46Z</dc:date>
    </item>
    <item>
      <title>Re: PAM ServiceNow Ticketing integration</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pam-servicenow-ticketing-integration/m-p/1409571#M84807</link>
      <description>&lt;P&gt;Hi @Froz Abdul Wahab Ameer Ahamed​&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You are right. In my understanding also it’s not with supported the native OOTB CyberArk DLL.&lt;/P&gt;&lt;P&gt;The component that handles the ticket validation which is a DLL file that makes the REST API call to ServiceNow is not customizable. The validation logic is hardcoded to check the&amp;nbsp;&lt;/P&gt;&lt;P&gt;Requested By CHG or INC.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please engage CyberArk counterpart and you can request to their Plugin development team to customize the module.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The self-hosted OOTB Ticketing Integration only supports Basic Authentication.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Again, please check with the Plugin development team if authentication method can be changed in a custom module.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope it helps !&lt;/P&gt;</description>
      <pubDate>Tue, 07 Oct 2025 05:51:19 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pam-servicenow-ticketing-integration/m-p/1409571#M84807</guid>
      <dc:creator>M.Vora780263</dc:creator>
      <dc:date>2025-10-07T05:51:19Z</dc:date>
    </item>
    <item>
      <title>Re: PAM ServiceNow Ticketing integration</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pam-servicenow-ticketing-integration/m-p/1409572#M84808</link>
      <description>&lt;P&gt;1) To validate if the ‘Username’ validation can be updated to ‘Assigned to’ for CHG and INC, instead of ‘Requested by’ or ‘Caller’.&lt;/P&gt;&lt;P&gt;In case of change ticket, its validate if username requesting the connection is also having change ticket requested by him.&lt;/P&gt;&lt;P&gt;in case of incident ticket, its validate if username requesting the connection is also matching with assigned to filed of the ticket used by him.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2) Online examples show the API call from CyberArk is using basic authentication.&amp;nbsp;&amp;nbsp;We cannot enable API access using basic auth without appropriate risks being raised and approved.&amp;nbsp;Is there any additional auth is permitted like OAUTH2 or Mutual Auth etc?&lt;/P&gt;&lt;P&gt;The API authentication done using the JWT and there is no flexibility for changing it as of now.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can develop your own code to fullfill required business requirement&lt;/P&gt;</description>
      <pubDate>Tue, 07 Oct 2025 05:56:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pam-servicenow-ticketing-integration/m-p/1409572#M84808</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-10-07T05:56:27Z</dc:date>
    </item>
    <item>
      <title>Re: PAM ServiceNow Ticketing integration</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pam-servicenow-ticketing-integration/m-p/1409573#M84809</link>
      <description>&lt;P&gt;1) To validate if the ‘Username’ validation can be updated to ‘Assigned to’ for CHG and INC, instead of ‘Requested by’ or ‘Caller’.&lt;/P&gt;&lt;P&gt;In case of change ticket, its validate if username requesting the connection is also having change ticket requested by him.&lt;/P&gt;&lt;P&gt;in case of incident ticket, its validate if username requesting the connection is also matching with assigned to filed of the ticket used by him.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2) Online examples show the API call from CyberArk is using basic authentication.&amp;nbsp;&amp;nbsp;We cannot enable API access using basic auth without appropriate risks being raised and approved.&amp;nbsp;Is there any additional auth is permitted like OAUTH2 or Mutual Auth etc?&lt;/P&gt;&lt;P&gt;The API authentication done using the JWT and there is no flexibility for changing it as of now.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can develop your own code to fullfill required business requirement&lt;/P&gt;</description>
      <pubDate>Tue, 07 Oct 2025 05:56:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pam-servicenow-ticketing-integration/m-p/1409573#M84809</guid>
      <dc:creator>SKumar_IIA1</dc:creator>
      <dc:date>2025-10-07T05:56:27Z</dc:date>
    </item>
    <item>
      <title>Re: PAM ServiceNow Ticketing integration</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pam-servicenow-ticketing-integration/m-p/1409574#M84810</link>
      <description>&lt;P&gt;Thanks @Malhar Vora​&amp;nbsp; and @Sumit Kumar​&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Oct 2025 06:08:24 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pam-servicenow-ticketing-integration/m-p/1409574#M84810</guid>
      <dc:creator>Ferro</dc:creator>
      <dc:date>2025-10-07T06:08:24Z</dc:date>
    </item>
  </channel>
</rss>

