Difference between revisions of "Manually disabling LDAP authentication"

Jump to navigation Jump to search
m
Re-worded.
m (Re-worded.)
Line 5: Line 5:
=== Symptoms and error messages ===
=== Symptoms and error messages ===


The documentation for enabling LDAP isn't perfect, and in CMOD version 9.0 and higher, enabling LDAP can cause OnDemand to not start up after issuing the "[[arssockd]] -S" command.  Of course, without being able to start Content Manager OnDemand, you can't log in to turn LDAP off.  If you check the console output, you might find errors like these:
The documentation for enabling LDAP isn't perfect, and in CMOD version 9.0 and higher, enabling LDAP can cause OnDemand to not start up after issuing the "[[arssockd]] -S" command, or refusing to allow logins.   
 
Of course, without being able to start Content Manager OnDemand or being able to log in, you can't turn LDAP off.  If you check the OnDemand Library Server's console output, you might find errors like these:


<code>
<code>
Line 13: Line 15:
</code>
</code>


Alternately, you may have enabled LDAP, and the server was able to start, but you're no longer able to log in, and you'd like to turn off LDAP so you can log in and figure out why.
If your server does start up, but you can't log in, you'll need to follow these instructions to turn off LDAP authentication, so you can try to figure out what went wrong.


These instructions will manipulate the contents of the CMOD database directly to disable LDAP so you can resume troubleshooting.  USE THESE INSTRUCTIONS WITH CAUTION.
These instructions will manipulate the contents of the CMOD database directly to disable LDAP.  USE THESE INSTRUCTIONS WITH CAUTION.


=== Directions ===
=== Directions ===

Navigation menu