<?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: How to create a Machine Connector that doesn't rely on an arbitrary name to attach the certificate? in Network Security Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/network-security-discussions/how-to-create-a-machine-connector-that-doesn-t-rely-on-an/m-p/1412914#M359</link>
    <description>&lt;P&gt;Hi @Simon Meadows​.  Names are not required and configureInstallationEndpoint has a different payload than that:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Field_Content_versions_oct20__068Vy000010i6KcIAI.png"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/94330i8C1E4A36FB9953DC/image-size/large?v=v2&amp;amp;px=999" role="button" title="Field_Content_versions_oct20__068Vy000010i6KcIAI.png" alt="Field_Content_versions_oct20__068Vy000010i6KcIAI.png" /&gt;&lt;/span&gt;If the sha256 thumbprint is what you need to configure the endpoint after the certificate has been installed, you can return that in the response for installCertifiateBundle and that will be provided to configureInstallationEndpoint.&lt;/P&gt;</description>
    <pubDate>Mon, 24 Nov 2025 13:18:14 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2025-11-24T13:18:14Z</dc:date>
    <item>
      <title>How to create a Machine Connector that doesn't rely on an arbitrary name to attach the certificate?</title>
      <link>https://live.paloaltonetworks.com/t5/network-security-discussions/how-to-create-a-machine-connector-that-doesn-t-rely-on-an/m-p/1412913#M358</link>
      <description>&lt;P&gt;I am building a new machine connector for use with Certificate Manager SaaS.&lt;/P&gt;&lt;P&gt;The Connecter breaks the certificate install process into four steps:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;testConnection&lt;/LI&gt;&lt;LI&gt;installCertificateBundle&lt;/LI&gt;&lt;LI&gt;configureInstallationEndpoint&lt;/LI&gt;&lt;LI&gt;discoverCertificates&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Each as seperate API calls to the connector on the vSat.&lt;/P&gt;&lt;P&gt;It is designed in a way that requires a user to give the certificate a name on the destination system.&lt;/P&gt;&lt;P&gt;installCertificateBundle is intended to put the certificate on the destination with the given name.&lt;/P&gt;&lt;P&gt;configureInstallationEndpoint is then intended to use that given name to attach the certificate to a web service/interface etc.&lt;/P&gt;&lt;P&gt;I believe this is all beased on the original F5 Big-IP connector so appears to be designed around that platform specifically.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The sysem I am building this for has no naming system for the certificates. It uniquely identifies them by their sha256 thumb-print.&lt;/P&gt;&lt;P&gt;As no information about the certificate except the user defined name is passed in the configureInstallationEndpoint call how can I identify the certificate that has just been installed in order to use it in the configureInstallationEndpoint stage and assign it to the service I need to?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 18 Nov 2025 14:49:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/network-security-discussions/how-to-create-a-machine-connector-that-doesn-t-rely-on-an/m-p/1412913#M358</guid>
      <dc:creator>SMeadows</dc:creator>
      <dc:date>2025-11-18T14:49:16Z</dc:date>
    </item>
    <item>
      <title>Re: How to create a Machine Connector that doesn't rely on an arbitrary name to attach the certificate?</title>
      <link>https://live.paloaltonetworks.com/t5/network-security-discussions/how-to-create-a-machine-connector-that-doesn-t-rely-on-an/m-p/1412914#M359</link>
      <description>&lt;P&gt;Hi @Simon Meadows​.  Names are not required and configureInstallationEndpoint has a different payload than that:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Field_Content_versions_oct20__068Vy000010i6KcIAI.png"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/94330i8C1E4A36FB9953DC/image-size/large?v=v2&amp;amp;px=999" role="button" title="Field_Content_versions_oct20__068Vy000010i6KcIAI.png" alt="Field_Content_versions_oct20__068Vy000010i6KcIAI.png" /&gt;&lt;/span&gt;If the sha256 thumbprint is what you need to configure the endpoint after the certificate has been installed, you can return that in the response for installCertifiateBundle and that will be provided to configureInstallationEndpoint.&lt;/P&gt;</description>
      <pubDate>Mon, 24 Nov 2025 13:18:14 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/network-security-discussions/how-to-create-a-machine-connector-that-doesn-t-rely-on-an/m-p/1412914#M359</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-11-24T13:18:14Z</dc:date>
    </item>
  </channel>
</rss>

