https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162019-04-01T08:07:59ZpfSense bugtrackerpfSense - Bug #9433: User directory authentication over LDAPS fails in 2.4.4_2https://redmine.pfsense.org/issues/9433?journal_id=403122019-04-01T08:07:59ZJim Pingle
<ul><li><strong>Category</strong> set to <i>User Manager / Privileges</i></li><li><strong>Status</strong> changed from <i>New</i> to <i>Not a Bug</i></li><li><strong>Priority</strong> changed from <i>High</i> to <i>Normal</i></li></ul><p>The Global Root CA is working fine here on 2.4.4-p2, I can't reproduce the problem as stated.</p>
<p>Problems like this almost invariably end up being DNS/hostname related. Please start a thread on <a class="external" href="https://forum.netgate.com">https://forum.netgate.com</a> to discuss the issue with your environment. If a specific bug can be identified, this issue can be reopened once we have enough information to reproduce the problem.</p>
<p>Also, due to <a class="issue tracker-4 status-3 priority-4 priority-default closed" title="Todo: Convert LDAP TLS setup from environment to LDAP_OPT_X_TLS_* set options (Resolved)" href="https://redmine.pfsense.org/issues/9417">#9417</a> you will probably need to run options 16 and 11 from the console/ssh (or reboot) after making changes to an SSL LDAP server. You can apply the commit ID from that issue (996a1ad90e5682bf881bafd8b75d1b1a7e3f7831) using the <a href="https://docs.netgate.com/pfsense/en/latest/development/system-patches.html" class="external">System Patches package</a> to see if that helps. Though the issue is targeted at 2.5.0, the patch applies to 2.4.4-p2 and works.</p> pfSense - Bug #9433: User directory authentication over LDAPS fails in 2.4.4_2https://redmine.pfsense.org/issues/9433?journal_id=403232019-04-01T13:34:22ZJT Gray
<ul></ul><p>Awesome, thanks - this fixed it for me!!</p>
<p>Jim Pingle wrote:</p>
<blockquote>
<p>The Global Root CA is working fine here on 2.4.4-p2, I can't reproduce the problem as stated.</p>
<p>Problems like this almost invariably end up being DNS/hostname related. Please start a thread on <a class="external" href="https://forum.netgate.com">https://forum.netgate.com</a> to discuss the issue with your environment. If a specific bug can be identified, this issue can be reopened once we have enough information to reproduce the problem.</p>
<p>Also, due to <a class="issue tracker-4 status-3 priority-4 priority-default closed" title="Todo: Convert LDAP TLS setup from environment to LDAP_OPT_X_TLS_* set options (Resolved)" href="https://redmine.pfsense.org/issues/9417">#9417</a> you will probably need to run options 16 and 11 from the console/ssh (or reboot) after making changes to an SSL LDAP server. You can apply the commit ID from that issue (996a1ad90e5682bf881bafd8b75d1b1a7e3f7831) using the <a href="https://docs.netgate.com/pfsense/en/latest/development/system-patches.html" class="external">System Patches package</a> to see if that helps. Though the issue is targeted at 2.5.0, the patch applies to 2.4.4-p2 and works.</p>
</blockquote>