Custom Authentication configuration file

jhh's Avatar


18 Jan, 2011 06:36 PM

I'm having the same problem but I don't know how to fix it. I'm running CentOS Linux. The server completely bypasses the custom install functionality and fails after presenting the Cascade server login screen with the message that it does not understand custom authentication. How do I fix this so that we can demo the beta.

  1. 1 Posted by Joel on 18 Jan, 2011 06:43 PM

    Joel's Avatar


    Do you have any administrator login that does not use custom authentication? If so, login via that user and replace the corrupted Custom Auth XML with the correct XML from your current production instance. If this is not possible, then simply remove the Custom Auth XML temporarily from your production instance before exporting a dump, so that the export does not contain Custom Auth XML at all. You can then place your XML back into your production instance after the dump completes, and use the new dump file to upgrade to the 6.8beta.


  2. 2 Posted by jhh on 20 Jan, 2011 08:31 PM

    jhh's Avatar

    The info provided fixed it. Thanks!

  3. Tim closed this discussion on 20 Jan, 2011 08:49 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac