<?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: Radius Auth Profile with PEAP-MsCHAPv2 in GlobalProtect Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/radius-auth-profile-with-peap-mschapv2/m-p/417866#M1504</link>
    <description>&lt;P&gt;Hi Sakhan,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Im looking at your first screenshot which shows PEAP Properties, you have chosen "Microsoft: Protected EAP (PEAP)" and I was curious to know why you've&amp;nbsp; also checked MSCHAPv2 under the less secure authentication methods. Is there a reason to that. In my setup I do not have anything checked under less secure authentication method and it works as intended.&lt;/P&gt;</description>
    <pubDate>Thu, 08 Jul 2021 17:19:21 GMT</pubDate>
    <dc:creator>Ranandaraj</dc:creator>
    <dc:date>2021-07-08T17:19:21Z</dc:date>
    <item>
      <title>Radius Auth Profile with PEAP-MsCHAPv2</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/radius-auth-profile-with-peap-mschapv2/m-p/351332#M433</link>
      <description>&lt;P&gt;Has anyone successfully integrated Radius Auth profile&amp;nbsp;PEAP-MsCHAPv2 with NPS or any other Radius platform?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have configured my Radius Auth Profile and attached relevant Cert profile to it as per below knowledgebase article.&lt;/P&gt;&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000CmkRCAS" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000CmkRCAS&lt;/A&gt;&lt;/P&gt;&lt;P&gt;However we are unable to establish successful authentication attempt for global protect user on radius auth profile, If I changed the Radius auth type to PAP it works fine.&lt;/P&gt;&lt;P&gt;Below is the NPS setting used shared by team managing NPS&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="NamalW_0-1600837232072.png" style="width: 400px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/27861i339FA886F9B9BE1B/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="NamalW_0-1600837232072.png" alt="NamalW_0-1600837232072.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 23 Sep 2020 05:00:55 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/radius-auth-profile-with-peap-mschapv2/m-p/351332#M433</guid>
      <dc:creator>Namalw</dc:creator>
      <dc:date>2020-09-23T05:00:55Z</dc:date>
    </item>
    <item>
      <title>Re: Radius Auth Profile with PEAP-MsCHAPv2</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/radius-auth-profile-with-peap-mschapv2/m-p/352301#M451</link>
      <description>&lt;P&gt;&lt;SPAN&gt;PEAP-MSCHAPv2 to work, a certificate will be required on the domain controller, which needs to be signed by an Internal PKI CA.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="windowsNPS.png" style="width: 999px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/27956i8FE87C556ECF2C3D/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="windowsNPS.png" alt="windowsNPS.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;As you can see above that my DC01 has a certificate issued by my Root CA SOS.local&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;On the firewall side, you should have the following configuration:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="radius-mschap.png" style="width: 603px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/27957iA1BF433E85CC1FEF/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="radius-mschap.png" alt="radius-mschap.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;From the screenshot above, we can see the certificate profile applied "PEAP-Cert", which will have by signing CA and authentication protocol is selected as PEAP-MSCHAPv2&lt;BR /&gt;&lt;BR /&gt;After the config above, you can create an authentication profile with the RADIUS profile above an apply it to your Portal or gateway or both.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Hope that helps!&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 25 Sep 2020 23:04:06 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/radius-auth-profile-with-peap-mschapv2/m-p/352301#M451</guid>
      <dc:creator>khans</dc:creator>
      <dc:date>2020-09-25T23:04:06Z</dc:date>
    </item>
    <item>
      <title>Re: Radius Auth Profile with PEAP-MsCHAPv2</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/radius-auth-profile-with-peap-mschapv2/m-p/417866#M1504</link>
      <description>&lt;P&gt;Hi Sakhan,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Im looking at your first screenshot which shows PEAP Properties, you have chosen "Microsoft: Protected EAP (PEAP)" and I was curious to know why you've&amp;nbsp; also checked MSCHAPv2 under the less secure authentication methods. Is there a reason to that. In my setup I do not have anything checked under less secure authentication method and it works as intended.&lt;/P&gt;</description>
      <pubDate>Thu, 08 Jul 2021 17:19:21 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/radius-auth-profile-with-peap-mschapv2/m-p/417866#M1504</guid>
      <dc:creator>Ranandaraj</dc:creator>
      <dc:date>2021-07-08T17:19:21Z</dc:date>
    </item>
  </channel>
</rss>

