Rick Vanderveer schrieb: > Thanks for the reply, Thomas. As my grandfather would say; "well, crap." :-) > > That forces me to re-think how clients and internal users login. As > a stop-gap, I've set it to the default authenticator (from > MoinMoin.auth import MoinAuth). Which brings me to my next question: > > Is there an easy way so that only I (or some other trusted admins) can > create user accounts?
you could disable the newaccount action and create users by the moin command on the server. If you need it web based you can hack the action macro and add a condition that a superuser account is required to call it. Also you can use a TextCha questions which only the community involved in the wiki content can answer. I do prefer the last solution. cheers Reimar I don't want any account self-created, I want > the handful to be created only by those with admin rights. I > understand how to set and configure the acl_rights_default so that > non-trusted users cannot view pages, but also don't want people even > trying to create accounts. Many versions ago, this was easily done by > setting the ACL on the UserPreferences page. But that's not used > anymore, obviously. Maybe restrict access to the newaccount action? > Or similar technique? (sorry, it's been a while since I've configured > a wiki in this way). > > -Rick > > > > > > On Sat, Sep 5, 2009 at 6:22 AM, Thomas Waldmann<tw-pub...@gmx.de> wrote: >> Hi Rick, >> >>> I'm trying to get a wiki configured that will allow multiple >>> authentication methods. According to HelpOnAuthentication, this >>> should be possible by combining multiple auths. >> It should be, but especially ldap auth is maybe not flexible enough and >> defaults to a rather "authoritative" behaviour: if it tells "no", it is >> "no". >> >> Changing this needs thinking through different scenarios, like: >> * mixing ldap and other authenticators >> * mixing different ldap authenticators >> * having multiple ldap authenticators with same content (like pdc, bdc) >> >> The problem is that I personally don't use ldap auth and have no test >> environment, thus well-tested improvements are very welcome. >> >>> When I merge the two, the standard auth users are no longer able to >>> log in. The LDAP users get an "Invalid username or password" error, >>> BUT does successfully log in (they're able to click the "clear >>> message" link and continue just fine). >> That is because you use it as last authenticator, the authenticator that >> ran before it already created a user object. >> >>> givenname_attribute=None, >>> surname_attribute=None, >>> aliasname_attribute=None, >>> email_attribute=None, >> You maybe want to use some of these, so it creates/updates user profile >> with the data from ldap. >> >>> tls_cacertdir='', >>> tls_cacertfile='', >>> tls_certfile='', >>> tls_keyfile='', >> Look there: http://hg.moinmo.in/moin/1.8/rev/e42fc41f71a4 >> >> Cheers, >> >> Thomas >> >> >> > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Moin-user mailing list Moin-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/moin-user
