<?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: REST API endpoint for publishing and pushing multi-port access rule in API / CLI Discussion</title>
    <link>https://community.checkpoint.com/t5/API-CLI-Discussion/REST-API-endpoint-for-publishing-and-pushing-multi-port-access/m-p/210203#M8449</link>
    <description>&lt;P&gt;Is the '&lt;SPAN&gt;service-ranges' parameter for the&amp;nbsp;add-access-rule REST API call used for that multi-port group configuration?&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 01 Apr 2024 18:20:15 GMT</pubDate>
    <dc:creator>pdn</dc:creator>
    <dc:date>2024-04-01T18:20:15Z</dc:date>
    <item>
      <title>REST API endpoint for publishing and pushing multi-port access rule</title>
      <link>https://community.checkpoint.com/t5/API-CLI-Discussion/REST-API-endpoint-for-publishing-and-pushing-multi-port-access/m-p/210202#M8448</link>
      <description>&lt;P&gt;Let's say we have to publish multile access rules to the Checkpoint that have the same source AND destination, but different ports.&amp;nbsp; Is there a REST API that we could use to send a 'group' publish to the Checkpoint?&amp;nbsp; So essentially, today with multiple individual publishes, we would see multiple individual rules published/installed on the Checkpoint, each with a single port number.&amp;nbsp; If the group publish/install feature is avaiable, we should only see one rule, that is for all requested different ports.&amp;nbsp; Same source and destination, but for multiple ports, that is.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Mon, 01 Apr 2024 18:11:53 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/API-CLI-Discussion/REST-API-endpoint-for-publishing-and-pushing-multi-port-access/m-p/210202#M8448</guid>
      <dc:creator>pdn</dc:creator>
      <dc:date>2024-04-01T18:11:53Z</dc:date>
    </item>
    <item>
      <title>Re: REST API endpoint for publishing and pushing multi-port access rule</title>
      <link>https://community.checkpoint.com/t5/API-CLI-Discussion/REST-API-endpoint-for-publishing-and-pushing-multi-port-access/m-p/210203#M8449</link>
      <description>&lt;P&gt;Is the '&lt;SPAN&gt;service-ranges' parameter for the&amp;nbsp;add-access-rule REST API call used for that multi-port group configuration?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 01 Apr 2024 18:20:15 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/API-CLI-Discussion/REST-API-endpoint-for-publishing-and-pushing-multi-port-access/m-p/210203#M8449</guid>
      <dc:creator>pdn</dc:creator>
      <dc:date>2024-04-01T18:20:15Z</dc:date>
    </item>
    <item>
      <title>Re: REST API endpoint for publishing and pushing multi-port access rule</title>
      <link>https://community.checkpoint.com/t5/API-CLI-Discussion/REST-API-endpoint-for-publishing-and-pushing-multi-port-access/m-p/210210#M8450</link>
      <description>&lt;P&gt;'service-ranges' isn't used for any configuration. It's only present in returned objects if you include "show-as-ranges":true in your call's body. I just confirmed /add-access-rule doesn't actually accept the show-as-ranges&amp;nbsp;key in the body, so the service-ranges key in the documentation for the return is a documentation bug.&lt;/P&gt;</description>
      <pubDate>Mon, 01 Apr 2024 19:30:54 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/API-CLI-Discussion/REST-API-endpoint-for-publishing-and-pushing-multi-port-access/m-p/210210#M8450</guid>
      <dc:creator>Bob_Zimmerman</dc:creator>
      <dc:date>2024-04-01T19:30:54Z</dc:date>
    </item>
    <item>
      <title>Re: REST API endpoint for publishing and pushing multi-port access rule</title>
      <link>https://community.checkpoint.com/t5/API-CLI-Discussion/REST-API-endpoint-for-publishing-and-pushing-multi-port-access/m-p/210216#M8451</link>
      <description>&lt;P&gt;To be sure I understand, it sounds like you're saying you add one rule per service, then publish, and you want the publish to look like it's a single rule instead of two or more. Publishing shows the changes made accurately. If you add multiple rules, it will always show multiple rules added.&lt;/P&gt;
&lt;P&gt;Why not just add a single rule with multiple services? Via HTTP, you simply stick an array of service object names or UUIDs into the "service" key. Via mgmt_cli, you have to deal with how mgmt_cli represents arrays and do "service.1 &amp;lt;name or UUID&amp;gt; service.2 &amp;lt;name or UUID&amp;gt; service.3 &amp;lt;name or UUID&amp;gt; ...".&lt;/P&gt;</description>
      <pubDate>Mon, 01 Apr 2024 19:39:34 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/API-CLI-Discussion/REST-API-endpoint-for-publishing-and-pushing-multi-port-access/m-p/210216#M8451</guid>
      <dc:creator>Bob_Zimmerman</dc:creator>
      <dc:date>2024-04-01T19:39:34Z</dc:date>
    </item>
    <item>
      <title>Re: REST API endpoint for publishing and pushing multi-port access rule</title>
      <link>https://community.checkpoint.com/t5/API-CLI-Discussion/REST-API-endpoint-for-publishing-and-pushing-multi-port-access/m-p/210218#M8452</link>
      <description>&lt;P&gt;So using the&amp;nbsp;&lt;SPAN&gt;add-access-rule REST API call, with the service parameter (screenshot attached) as a list?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 01 Apr 2024 19:47:43 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/API-CLI-Discussion/REST-API-endpoint-for-publishing-and-pushing-multi-port-access/m-p/210218#M8452</guid>
      <dc:creator>pdn</dc:creator>
      <dc:date>2024-04-01T19:47:43Z</dc:date>
    </item>
    <item>
      <title>Re: REST API endpoint for publishing and pushing multi-port access rule</title>
      <link>https://community.checkpoint.com/t5/API-CLI-Discussion/REST-API-endpoint-for-publishing-and-pushing-multi-port-access/m-p/210221#M8453</link>
      <description>&lt;P&gt;That's also in the return section. Go to the top of the page, and collapse the sections as you go down. An expanded section has a white V in a gray circle, and a collapsed section has a white &amp;gt; in a gray circle. Click on the gray circle to toggle. Once you have everything collapsed, expand the Arguments section. The "service" key accepts string or List: string. Both forms want the string to be either a name or a UUID of an appropriate object.&lt;/P&gt;</description>
      <pubDate>Mon, 01 Apr 2024 19:53:27 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/API-CLI-Discussion/REST-API-endpoint-for-publishing-and-pushing-multi-port-access/m-p/210221#M8453</guid>
      <dc:creator>Bob_Zimmerman</dc:creator>
      <dc:date>2024-04-01T19:53:27Z</dc:date>
    </item>
    <item>
      <title>Re: REST API endpoint for publishing and pushing multi-port access rule</title>
      <link>https://community.checkpoint.com/t5/API-CLI-Discussion/REST-API-endpoint-for-publishing-and-pushing-multi-port-access/m-p/210223#M8454</link>
      <description>&lt;P&gt;OK, thanks.&lt;/P&gt;</description>
      <pubDate>Mon, 01 Apr 2024 20:06:32 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/API-CLI-Discussion/REST-API-endpoint-for-publishing-and-pushing-multi-port-access/m-p/210223#M8454</guid>
      <dc:creator>pdn</dc:creator>
      <dc:date>2024-04-01T20:06:32Z</dc:date>
    </item>
  </channel>
</rss>

