<?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 NX5500 Controller LDAPS certificate issues with Windows AD in ExtremeWireless (WiNG)</title>
    <link>https://community.extremenetworks.com/t5/extremewireless-wing/nx5500-controller-ldaps-certificate-issues-with-windows-ad/m-p/26890#M2713</link>
    <description>A NX5500 has been configured to use LDAP(S) authentication for admins logging into the management UI portal. I can get the port 389 non-SSL working but not the 636 SSL. &lt;BR /&gt;
&lt;BR /&gt;
I have gotten a publicly signed certificate from a CSR generated on the NX5500, and uploaded the CA from the to the NX5500 along with the signed certificate back from said CA and paired them as a trustpoint. When I try to log in, I get an error that I could not - and in my Windows LDAP server I see an error "the certificate chain was issued by an authority that is not trusted."&lt;BR /&gt;
&lt;BR /&gt;
I've also issued a certificate signed by my non-public CA and used that certificate on the NX5500, and that throws the same error in the Windows logs. I'm at a loss.&lt;BR /&gt;
&lt;BR /&gt;
This could be my lack of knowledge on SSL/Certs - but I have an identical setup working on other devices using LDAP and I don't have this issue. Is this the correct set up ? What isn't being trusted?</description>
    <pubDate>Tue, 18 Dec 2018 11:53:00 GMT</pubDate>
    <dc:creator>Aaron_Becker</dc:creator>
    <dc:date>2018-12-18T11:53:00Z</dc:date>
    <item>
      <title>NX5500 Controller LDAPS certificate issues with Windows AD</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/nx5500-controller-ldaps-certificate-issues-with-windows-ad/m-p/26890#M2713</link>
      <description>A NX5500 has been configured to use LDAP(S) authentication for admins logging into the management UI portal. I can get the port 389 non-SSL working but not the 636 SSL. &lt;BR /&gt;
&lt;BR /&gt;
I have gotten a publicly signed certificate from a CSR generated on the NX5500, and uploaded the CA from the to the NX5500 along with the signed certificate back from said CA and paired them as a trustpoint. When I try to log in, I get an error that I could not - and in my Windows LDAP server I see an error "the certificate chain was issued by an authority that is not trusted."&lt;BR /&gt;
&lt;BR /&gt;
I've also issued a certificate signed by my non-public CA and used that certificate on the NX5500, and that throws the same error in the Windows logs. I'm at a loss.&lt;BR /&gt;
&lt;BR /&gt;
This could be my lack of knowledge on SSL/Certs - but I have an identical setup working on other devices using LDAP and I don't have this issue. Is this the correct set up ? What isn't being trusted?</description>
      <pubDate>Tue, 18 Dec 2018 11:53:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/nx5500-controller-ldaps-certificate-issues-with-windows-ad/m-p/26890#M2713</guid>
      <dc:creator>Aaron_Becker</dc:creator>
      <dc:date>2018-12-18T11:53:00Z</dc:date>
    </item>
  </channel>
</rss>

