On Friday 16 November 2001 16:49, you wrote: > I use midgard/nadmin as the admin interface of a portal, with 3-5 > admins, which are midgard users. > > Besides this, I have thousands of users of the site, which I don't > want to store in midgard database. (I still don't have a feel how > midgard handles thousands of users, or hundreds of thousands of > articles...) I want to authenticate these users to reach various parts > of my site based on the users' groups/categories/whatever. So I need a > method to mark my pages (included all subpages) that these pages can > be reached only as a user group 'A' etc...
That requires pretty hefty reworking. 1. We don't have read access controls right now (other than sitegroups if you want to label them that way) 2. Having users outside the midgard database will need awkward hacks to work. Midgard has an internal idea of what groups a person belongs to. Without that, the user will have write access to nothing. Then there's the issue that at multiple places we do calls like "SELECT page.id, person.name WHERE page.id=3 AND page.author=person.id". I'm not saying this is necesarily desired, but it's the way it's always worked. If the person record does not exist in the database, the query above will show up empty, even though the article exists. On the positive side, the scripting layer is going to facilitate changing things like this while not breaking everything. If people have ideas, or requirements, now's the time to subscribe to dev@ and make sure Alexander knows about them. I recovered my earlier midgard-pam patch; maybe it's of use to you. It wasn't tested then, and it almost certainly won't apply cleanly now (since I made changed to the midgard login structure). It's small, so you'll find it attached. Emile
midgard-pam.tar.gz
Description: Patch to pamify midgard. Old.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
