<?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 Renewal requests for NDE in Network Security Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/network-security-discussions/renewal-requests-for-nde/m-p/1420150#M717</link>
    <description>&lt;P&gt;We have a use casein Venafi NDE, where the renewal request is rejected because TPP is mandating that the password be supplied again as the device can't be configured to supply it on the renewal.According to RFC8894, a challenge Password is required for initial enrollment. However, for certificate renewal the existing certificate is used for authentication and the challenge Password is optional. Do we have a work around for this issue?&lt;/P&gt;</description>
    <pubDate>Mon, 10 Mar 2025 16:12:40 GMT</pubDate>
    <dc:creator>Aparna_N</dc:creator>
    <dc:date>2025-03-10T16:12:40Z</dc:date>
    <item>
      <title>Renewal requests for NDE</title>
      <link>https://live.paloaltonetworks.com/t5/network-security-discussions/renewal-requests-for-nde/m-p/1420150#M717</link>
      <description>&lt;P&gt;We have a use casein Venafi NDE, where the renewal request is rejected because TPP is mandating that the password be supplied again as the device can't be configured to supply it on the renewal.According to RFC8894, a challenge Password is required for initial enrollment. However, for certificate renewal the existing certificate is used for authentication and the challenge Password is optional. Do we have a work around for this issue?&lt;/P&gt;</description>
      <pubDate>Mon, 10 Mar 2025 16:12:40 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/network-security-discussions/renewal-requests-for-nde/m-p/1420150#M717</guid>
      <dc:creator>Aparna_N</dc:creator>
      <dc:date>2025-03-10T16:12:40Z</dc:date>
    </item>
  </channel>
</rss>

