Hi, Yes, they can.
Access to news groups on the server is controlled by _access.conf_, which you can edit via the Web interface. Usually the database is used only to edit users and their user groups. Where authentication is coming from the database, you use $lookup$ entries. Authentication in users.dat only requires a username and password in that file. E.g. *:read,post:$lookup$:$lookup$:* 10.*:read,post:bob:letmein:* In the above example, usergroups aren't being used, and anyone with a matching username and password from the external authentication database (ODBCAuth in your case) can read and post to any groups. Users from 10.* (10.0.0.0/8) can also read and post when using the username and password bob/letmein. - Roydon L. <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>... > Thanks for your suggestion! > > So can ODBCAuth be running together with the default users.dat? > > Many thanks, > > > > "Netwin Support" <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED] > > Hi, > > > > It depends on what you want to do specifically. If you were interested in > > giving your customers an interface in which they could modify their > details, > > then you'd possibly want to investigate using PHP (with ADODB) or another > > scripting language to add support to your templates. > > > > If however you simply wanted administrative access to all your data, you > > could use a Web-based database access tool. I'm not familiar with any of > > these myself, but do know that various options exist for MySQL and > > PostgreSQL. > > > > Most of the database tools I have seen are PHP or Perl based, so > server-side > > scripting of some kind would probably be necessary. > > > > - Roydon L. > > > > <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>... > > > Thanks a lot. > > > > > > Excuse me, what are the numerous tools? > > > > > > Many thanks, > > > > > > "Netwin Support" <[EMAIL PROTECTED]> wrote in message > > > news:[EMAIL PROTECTED] > > > > The authentication modules are not managed through this interface as > > they > > > > are designed for simple authentication tasks and to be easily written > by > > > > users where necessary. The protocol does allow for limited > manipulation > > of > > > > users, but is not required of all authentication modules. > > > > > > > > Most modules require some configuration to work, of varying > complexity. > > > > > > > > There are numerous tools available for manipulating databases via the > > Web > > > > which may be suitable if you need to control the user database in this > > > way. > > > > > > > > - Roydon L. > > > > > > > > <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>... > > > > > For users.dat, it's > > > > > > > > > > user:password:manager access(none,full):managed groups:full > > > > name:usergroups > > > > > > > > > > How about the manager access setting for ODBCAuth? > > > > > > > > > > Many thanks, > > > > > > > > > > > > > > > "Support Auckland" <[EMAIL PROTECTED]> wrote in message > > > > > news:[EMAIL PROTECTED] > > > > > > At 02:35 PM 12/11/2003 +0800, you wrote: > > > > > > >Also for the ODBCAuth setting, the groups can be translated as > > > > > > >field_translate xxxx groups > > > > > > > > > > > > > >How about the translation of access right? > > > > > > >Is it > > > > > > >field_translate xxxx access? > > > > > > > > > > > > Sorry, I'm not sure what you mean by 'access right' in this > context > > ? > > > > > > > > > > > > chrisP. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
