<div dir="ltr"><div><div>Does anyone have instructions on how to troubleshoot logging into the 389-console?</div><div><br></div><div>I haven't made any changes to 389 Directory Server (version 389-ds-1.2.2-1.el6.noarch) for over a week.</div>
<div><br></div><div>The change I made was to enable the directory server to run on port 636, and drop support for port 389. After making those changes I am positive that there was no ill effect because I was able to successfully login to the console and create a test user account using POSIX values.</div>
<div><br></div><div><br></div><div>Today is the first time since the 26 March (today is 3 April) that I have attempted to log back into the console.</div><div><br></div><div><br></div><div>I can no longer perform "ldapsearch -x -Z" while I am logged in as root on the server itself.</div>
<div><br></div><div>On the console login box I have the following:</div><div><br></div><div>cn=Directory Manager</div><div><password_for_DM></div><div><a href="http://localhost:9830/">http://localhost:9830/</a></div>
<div><br></div><div><br></div><div>However the error I get back is:</div><div><br></div><div>Cannot logon because of an incorrect User ID, Incorrect password or Directory problem.</div><div><br></div><div>Http Exception:</div>
<div>Response: HTTP/1.1 401 Authentication Required</div><div>Status: 401</div><div>URL: <a href="http://localhost:9830/admin-server/authenticate">http://localhost:9830/admin-server/authenticate</a></div><div><br></div>
<div>Any ideas of how to troubleshoot this further, more importantly fix the issue I am having with logging in?</div></div><div><br></div><br clear="all"><div><div dir="ltr">--------------------------<br><font color="#000099" size="4">Warron French<br>
<font size="4">703.967.8936(c)<br><font size="4">571.307.5311(<font size="4">W)<br><font size="4">703.393.7275(h)</font><br></font></font></font></font></div></div>
</div>