<?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: Any with Success? - Radius for 2 domains - trying to consolidate SSIDs in Aerohive Migrated Content</title>
    <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/any-with-success-radius-for-2-domains-trying-to-consolidate/m-p/77083#M7328</link>
    <description>&lt;P&gt;To answer my own question for the benefit of anyone interested, or suggested improvement(s):&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The Aerohive Radius Proxy appears to be basically designed to remove the need for CAL licenses for IAS/NPS servers prior to Win 2012 - that was ruled out.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;NPS ( as stand alone proxy only, or combined with proxy &amp;amp; auth rules ) can be configured to proxy radius requests by using matching rules in the "Connection Request Policies".  By matching rules to values in the User Name field I can redirect any radius request to the proper domain NPS server(s).&lt;/P&gt;</description>
    <pubDate>Fri, 10 May 2019 22:34:40 GMT</pubDate>
    <dc:creator>k_berrien</dc:creator>
    <dc:date>2019-05-10T22:34:40Z</dc:date>
    <item>
      <title>Any with Success? - Radius for 2 domains - trying to consolidate SSIDs</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/any-with-success-radius-for-2-domains-trying-to-consolidate/m-p/77082#M7327</link>
      <description>&lt;P&gt;I'd love to consolidate 2 SSID's with a NPS radius server behind each, on separate domains.  I do have a 1 way trust on domain A to B.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is anyone running such a configuration with success?  At this point I haven't looked into it in depth, but I suspect with the 1 way trust I could get 1 NPS to query data from both domains - but I'm concerned about any   "domain/user"  issues,  or duplicate names. We do both user &amp;amp; machine ID auth on both radius connections.  Perhaps a creative use of the RADIUS Proxy?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Since I can imagine ways in which it might work, and things that might not.. I thought I'd toss a quick - anyone doing this successfully - query out first.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thanks!&lt;/P&gt;</description>
      <pubDate>Fri, 03 May 2019 00:53:35 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/any-with-success-radius-for-2-domains-trying-to-consolidate/m-p/77082#M7327</guid>
      <dc:creator>k_berrien</dc:creator>
      <dc:date>2019-05-03T00:53:35Z</dc:date>
    </item>
    <item>
      <title>Re: Any with Success? - Radius for 2 domains - trying to consolidate SSIDs</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/any-with-success-radius-for-2-domains-trying-to-consolidate/m-p/77083#M7328</link>
      <description>&lt;P&gt;To answer my own question for the benefit of anyone interested, or suggested improvement(s):&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The Aerohive Radius Proxy appears to be basically designed to remove the need for CAL licenses for IAS/NPS servers prior to Win 2012 - that was ruled out.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;NPS ( as stand alone proxy only, or combined with proxy &amp;amp; auth rules ) can be configured to proxy radius requests by using matching rules in the "Connection Request Policies".  By matching rules to values in the User Name field I can redirect any radius request to the proper domain NPS server(s).&lt;/P&gt;</description>
      <pubDate>Fri, 10 May 2019 22:34:40 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/any-with-success-radius-for-2-domains-trying-to-consolidate/m-p/77083#M7328</guid>
      <dc:creator>k_berrien</dc:creator>
      <dc:date>2019-05-10T22:34:40Z</dc:date>
    </item>
  </channel>
</rss>

