UserDb, GUF, LoginManager, etc, which one?
Hi there, What I want is an acl_users equivalent that has an SQL database backend. I want an easy to understand, easy to install solution for this that has some kind of future in Zope land. Currently I'm deploying 2.1 but that should change into 2.2 eventually. UserDb isn't developed anymore. Besides, it might not work for 2.2. (does it?) GenericUserFolder is not developed anymore. Besides, it might not work for 2.2. (does it?) LoginManager is being developed. *But* it is dependent on ZPatterns, which is: * Another prerequisite * far too much for me to swallow right now. It sorts of doubles Zope's already not insignificant level of jargon and confusion. * under heavy development; lots of changes happening all the time, invalidating APIs etc. * needs a C module to be compiled. On Linux (development platform) that's okay, but it's not on my current deployment platform, Windows NT. I don't have a C compiler there. So what do I do if I want an SQL backend for my acl_users folder? This part of Zope seems to be becoming ever *more* complicated; the past seems to have been actually easier and simpler in this case. I just want to dump in a product, do minimal configuration, and be done with it. Is there any solution to my problem? Do I have to risk installing development versions of LoginManager/ZPatterns, or risk installing something that's not being developed anymore? Is there another way out? Regards, Martijn
At 05:58 PM 8/14/00 +0200, Martijn Faassen wrote:
What I want is an acl_users equivalent that has an SQL database backend. I want an easy to understand, easy to install solution for this that has some kind of future in Zope land. Currently I'm deploying 2.1 but that should change into 2.2 eventually.
Haven't needed to do this particular task myself, but I'll venture an approach. Based on code inspection rather than having a working solution, so take it with a grain of salt. If I were looking at this, I'd consider coding a specific solution right in Python. Not try to make it generic, through-the-web, or customizable, but something very simple does the specific job of looking up users directly from your particular database. Take a look at the interface in AccessControl/User.py, you'll see it's straightforward. I'd try creating my own user folder class which subclasses from BasicUserFolder just like UserFolder does. When asked for a user, such as by a getUser() method call, I'd try returning a SimpleUser object with the fields filled in from my database. Andrew
On Mon, 14 Aug 2000, Martijn Faassen wrote:
Hi there,
What I want is an acl_users equivalent that has an SQL database backend. I want an easy to understand, easy to install solution for this that has some kind of future in Zope land. Currently I'm deploying 2.1 but that should change into 2.2 eventually.
UserDb isn't developed anymore. Besides, it might not work for 2.2. (does it?)
i'm using userdb on 2.2.0 and it has been smooth sailing. setup is easy. but there are several drawbacks: -password is not encrypted. -it's not maintained - probably means that it's stable. until a new version of zope changes this, of course. i've tried GUF, but decided to stick with UserDB until i really have to change. login manager, i havenot tried yet note: userdb are not installed on a fresh zope2.2.0, but upgraded from 2.1.6. but i do remember installing on a fresh zope2.2.0 and encountered no problems.
[various folks basically suggest using UserDb and give useful tips] Okay, thanks for the suggestions, folks -- UserDb it will be, then! Regards, Martijn
participants (3)
-
Andrew Wilcox -
Bak ＠ kedai -
Martijn Faassen