<?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: Okta has 400+  IPs that are all /32.  Looking for an EDL solution in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/okta-has-400-ips-that-are-all-32-looking-for-an-edl-solution/m-p/485443#M104522</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/86594"&gt;@SteveKrall&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;They actually publish this information &lt;A href="https://s3.amazonaws.com/okta-ip-ranges/ip_ranges.json" target="_self"&gt;HERE&lt;/A&gt;&amp;nbsp;in JSON format. You could easily create a script that regularly pulls this list and feeds it into your EDL solution or add those addresses with a tag like Okta and then use an address-group in your policy.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 06 May 2022 14:04:32 GMT</pubDate>
    <dc:creator>BPry</dc:creator>
    <dc:date>2022-05-06T14:04:32Z</dc:date>
    <item>
      <title>Okta has 400+  IPs that are all /32.  Looking for an EDL solution</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/okta-has-400-ips-that-are-all-32-looking-for-an-edl-solution/m-p/485321#M104516</link>
      <description>&lt;P&gt;Has anybody figured out an edl to allow communications to Okta without manually entering the whole list?&amp;nbsp; My customer is using Okat for MFA and the Okta Portal uses a whitelist so they have policies that anything hitting Okta should use ip x.x.x.x.&amp;nbsp; This is legacy config from a newly replaced firewall.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;FQDN Address objects are only reporting 2 IPs&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;SK&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 05 May 2022 23:42:30 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/okta-has-400-ips-that-are-all-32-looking-for-an-edl-solution/m-p/485321#M104516</guid>
      <dc:creator>SteveKrall</dc:creator>
      <dc:date>2022-05-05T23:42:30Z</dc:date>
    </item>
    <item>
      <title>Re: Okta has 400+  IPs that are all /32.  Looking for an EDL solution</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/okta-has-400-ips-that-are-all-32-looking-for-an-edl-solution/m-p/485443#M104522</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/86594"&gt;@SteveKrall&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;They actually publish this information &lt;A href="https://s3.amazonaws.com/okta-ip-ranges/ip_ranges.json" target="_self"&gt;HERE&lt;/A&gt;&amp;nbsp;in JSON format. You could easily create a script that regularly pulls this list and feeds it into your EDL solution or add those addresses with a tag like Okta and then use an address-group in your policy.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 06 May 2022 14:04:32 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/okta-has-400-ips-that-are-all-32-looking-for-an-edl-solution/m-p/485443#M104522</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2022-05-06T14:04:32Z</dc:date>
    </item>
  </channel>
</rss>

