Question

.Hi, I'm playing around with a TWiki installation on a web hosting account. (I plan on sharing my experiences with the particular service on TWiki.org soon.)

I was wondering: Is there a group automatically maintained that holds all registered users? Or does such a group have to be manually maintained?

Thanks!

• TWiki version: Dec, 2001
• Web server: Apache
• Server OS: Red Hat Linux
• Web browser: IE 5.1
• Client OS: Mac OS X

-- MikaelBehrens - 06 Apr 2002

Answer

There is no TWikiGroup per se, however you probably should be able to work around this. For example, if you want to prevent guest logins from editing a web say * Set DENYWEBCHANGE = Main.TWikiGuest in the WebPreferences.

If you want to compile a list of all users you can do that with a FormattedSearch that scans for all topics in the Main web that have a * Email: bullet.

-- PeterThoeny - 11 Apr 2002

Reading this post gives me an idea on how to deal with the issues I'm currently working on.

I'm running TWiki on an intranet server (linux, apache) and am authenticating using mod_auth_pam with Require valid-user set at the root directory and propagating down to everything, including TWiki.

I'm left with two problems. One is that I can't seem to force people to register before editing a page. It seems that since apache passes a REMOTE_USER of pmelnikow to TWiki, it's happy to let me operate as Main.pmelnikow instead of requiring me to register Main.PaulMelnikow, setting pmelnikow as my intranet login.

I tried doing * Set DENYWEBCHANGE = Main.TWikiGuest , which didn't work, since I really seemed to be Main.pmelnikow and not Main.TwikiGuest.

It sounds like creating some sort of "all users" group (perhaps using FormattedSearch as you recommend) would allow me to work around this. However, this seems like it would be a really common problem, which makes me think that I'm just going about it thr wrong way, or that there's a more elegant way to do it. (For example, can I get TWiki to write out an htaccess file with require user lines for all the intranet users it knows about?)

Thanks

-- PaulMelnikow - 19 Jul 2002

Idea: You could hack the edit and attach script to redirect to an oops message if the user has not registered in TWiki. That way users would need to register to get a WikiName, even though all users are already authenticated. The critera for non registered user could be a regex detecting authenticated names that start in lowercase. For example, $theRemoteUser has pmelnikow; users are initialized after TWiki::initialize(), so $userName is Main.pmelnikow if the user has not registered, or Main.PaulMelnikow if he is. The regex test could be applied to $userName directly after TWiki::initialize().

See also Codev.UseLoginNames

-- PeterThoeny - 23 Jul 2002

A group like this would be great for making access control easier. Has anyone implemented a way for this to happen in the last 4 years since this topic was commented on? If not I suppose it wouldn't be too hard to have TWikiRegistrationAgent add to a list. Or any other suggestions on implementation?

-- GregPendlebury - 14 Nov 2006

No code yet. Feel free to open an enhancement request in the Codev web. An AllRegisteredUsersGroup would be useful to have (could be done implicit with a TWiki internal test, e.g. without the need to update the AllRegisteredUsersGroup at registration time.)

-- PeterThoeny - 14 Nov 2006

Still kind of new to this, but I think this works : AllUsersGroup

-- GregPendlebury - 14 Nov 2006

Yep, that is how it works. (I renamed the topic from Codev.AllUsersGroupHelpful to Codev.AllUsersGroup.)

-- PeterThoeny - 14 Nov 2006