<?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 UserID WinRM-HTTPS and Kerberos in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/userid-winrm-https-and-kerberos/m-p/550899#M112252</link>
    <description>&lt;P&gt;&lt;SPAN class="uir-field inputreadonly uir-resizable"&gt;I tried generating a self signed certificate on the firewall and installed this on the domain controller and assigned it to WinRM-HTTPS. This worked but I can’t figure out why it’s rejecting the certificate from our internal CA.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 25 Jul 2023 11:27:13 GMT</pubDate>
    <dc:creator>s0lselcia</dc:creator>
    <dc:date>2023-07-25T11:27:13Z</dc:date>
    <item>
      <title>UserID WinRM-HTTPS and Kerberos</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/userid-winrm-https-and-kerberos/m-p/550899#M112252</link>
      <description>&lt;P&gt;&lt;SPAN class="uir-field inputreadonly uir-resizable"&gt;I tried generating a self signed certificate on the firewall and installed this on the domain controller and assigned it to WinRM-HTTPS. This worked but I can’t figure out why it’s rejecting the certificate from our internal CA.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 25 Jul 2023 11:27:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/userid-winrm-https-and-kerberos/m-p/550899#M112252</guid>
      <dc:creator>s0lselcia</dc:creator>
      <dc:date>2023-07-25T11:27:13Z</dc:date>
    </item>
    <item>
      <title>Re: UserID WinRM-HTTPS and Kerberos</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/userid-winrm-https-and-kerberos/m-p/550910#M112254</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/283399"&gt;@s0lselcia&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Not a whole lot of information here.&amp;nbsp;&lt;EM&gt;&lt;STRONG&gt;What&amp;nbsp;&lt;/STRONG&gt;&lt;/EM&gt;is rejecting the certificate from your internal CA, the domain controller or the firewall? Assuming it's the firewall since that makes the most sense, did you go through and verify that you're using a working certificate profile under 'Connection Security' so the firewall can accept the presented certificate?&lt;/P&gt;</description>
      <pubDate>Tue, 25 Jul 2023 13:13:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/userid-winrm-https-and-kerberos/m-p/550910#M112254</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2023-07-25T13:13:47Z</dc:date>
    </item>
    <item>
      <title>Re: UserID WinRM-HTTPS and Kerberos</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/userid-winrm-https-and-kerberos/m-p/551094#M112269</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/43480"&gt;@BPry&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you for the reply&lt;/P&gt;
&lt;P&gt;Sorry I didn't give much information. The Server monitoring is showing "connection refused", the certificate profile under 'Connection Security' works with a certificate created by the firewall, but not with the CA created one.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 26 Jul 2023 13:38:45 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/userid-winrm-https-and-kerberos/m-p/551094#M112269</guid>
      <dc:creator>s0lselcia</dc:creator>
      <dc:date>2023-07-26T13:38:45Z</dc:date>
    </item>
  </channel>
</rss>

