<?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: Discovery Service limit in TLS Protect Cloud in Network Security Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/network-security-discussions/discovery-service-limit-in-tls-protect-cloud/m-p/1420802#M858</link>
    <description>Hi @S Oakley , thank you so much for sharing this on the community! Its always helpful to share this information to alert our team or others using the product. I heard from the Venafi team that this was indeed a bug that occurred if you had more than 100 services. The bug was addressed and customers should not need to reach out to support to increase the Discovery Service limit anymore. If anyone does run into this issue, dont hesitate to reach out to Support through the Venafi customer portal (success.venafi.com) or by emailing support@venafi.com.</description>
    <pubDate>Wed, 17 May 2023 14:04:59 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2023-05-17T14:04:59Z</dc:date>
    <item>
      <title>Discovery Service limit in TLS Protect Cloud</title>
      <link>https://live.paloaltonetworks.com/t5/network-security-discussions/discovery-service-limit-in-tls-protect-cloud/m-p/1420801#M857</link>
      <description>Just wanted to share an issue we recently experienced in case anyone else is having the same problem and maybe doesnt even realise it.It seems there is a hidden limit to the number of discovery services you can set up in TLS Protect Cloud, (deleted services still count towards the limit, which seems to be around 100). Once this limit is reachedyou can still set upnew discovery services but theywill display 0 certificates discovered, even if in the background certificates are being discovered.Theissue was resolved by support increasing the Discovery Service limit.</description>
      <pubDate>Wed, 10 May 2023 08:17:18 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/network-security-discussions/discovery-service-limit-in-tls-protect-cloud/m-p/1420801#M857</guid>
      <dc:creator>S.Oakley156848</dc:creator>
      <dc:date>2023-05-10T08:17:18Z</dc:date>
    </item>
    <item>
      <title>Re: Discovery Service limit in TLS Protect Cloud</title>
      <link>https://live.paloaltonetworks.com/t5/network-security-discussions/discovery-service-limit-in-tls-protect-cloud/m-p/1420802#M858</link>
      <description>Hi @S Oakley , thank you so much for sharing this on the community! Its always helpful to share this information to alert our team or others using the product. I heard from the Venafi team that this was indeed a bug that occurred if you had more than 100 services. The bug was addressed and customers should not need to reach out to support to increase the Discovery Service limit anymore. If anyone does run into this issue, dont hesitate to reach out to Support through the Venafi customer portal (success.venafi.com) or by emailing support@venafi.com.</description>
      <pubDate>Wed, 17 May 2023 14:04:59 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/network-security-discussions/discovery-service-limit-in-tls-protect-cloud/m-p/1420802#M858</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2023-05-17T14:04:59Z</dc:date>
    </item>
  </channel>
</rss>

