On Thu, Aug 05, 1999 at 12:09:04PM -0500, Jason Jones wrote:
I just changed my user database schema to match that of the UserDB product,
First note: Jason, you can change UserDb to match your schema, instead of the other way around. I didn't notice this the first time I fired up UserDb. You open your acl_users folder, and click the "Properties" tag. Then, you can edit the ZSQL methods used to access the db. Unless you just mean you added a field somewhere to store Zope roles in, and already knew all this, sorry. ;-)
and installed UserDB with cookie-based authentication. Immediately after doing that everything became inaccessible. Now, I get the response:
Hmm, I haven't done cookies yet. Perhaps this is it. You do have cookie acceptance turned on in your browser? (just checking) <SNIP traceback>
I set up the UserDB folder at the top level of the object heirarchy, is this the problem? Note, the superuser login no longer works and basically I can't access Zope at all.
I've got it as the toplevel, as well. You sure the superuser doesn't work? It still does for me.
Any suggestions would be greatly appreciated (especially how I could get back into Zope).
DC people? Any hints on how to crack root? ;-) Just kidding. Although, there may be some way to access the ZORB from a python prompt, and clear the 'use cookies' attribute on the acl_user object, which might let you back in. Although UserDb is an unsupported product, it strikes me that the superuser login is supposed to bypass the toplevel User Folder, whatever it does. Otherwise, you can't use it to fix broken User Folders ;-) Ross -- Ross J. Reedstrom, Ph.D., <reedstrm@rice.edu> NSBRI Research Scientist/Programmer Computer and Information Technology Institute Rice University, 6100 S. Main St., Houston, TX 77005