problems by defining the password file, posted by Marcel Pils on Thu Aug 15 13:00:20 2002
|
i work on Windows2000
part of my elog.cfg:
Passwort file = c:\elog\passwd.txt
Self register = 1
Guest user commands = config, admin, logout
file system:
- i created an emty file with name passwd.txt
problem:
- if i use the link "Register as new user" on login, it does not work.
- if i login as guest user and choose the menu config, it only
display the attributes Login_name, Full_name and Email.
So i kann not create user.
what should i do ?
what are my mistakes ?
Can you attache as sample password file ? |
Re: problems by defining the password file, posted by Marcel Pils on Thu Aug 15 18:00:36 2002
|
in Unix:
i fixed the problem by defining a password file entry like 'user1::::'.
then i defined 'admin user = user1' in elogd.cfg.
then i connected with login name 'user1' and created new user (as admin).
in Windows2000:
if i do this steps and i save the new user, it fails. the server service
crash down.
> i work on Windows2000
>
> part of my elog.cfg:
>
> Passwort file = c:\elog\passwd.txt
> Self register = 1
> Guest user commands = config, admin, logout
>
> file system:
>
> - i created an emty file with name passwd.txt
>
> problem:
>
> - if i use the link "Register as new user" on login, it does not work.
> - if i login as guest user and choose the menu config, it only
> display the attributes Login_name, Full_name and Email.
> So i kann not create user.
>
> what should i do ?
> what are my mistakes ?
>
> Can you attache as sample password file ? |
logging, posted by tony summerfelt on Thu Aug 15 20:21:17 2002
|
is it possible to add ip information into the logging? that's something i was working on already but never finished...now that there's logging already added :) |
password file and self register, posted by eric wooten on Fri Aug 16 09:03:24 2002
|
I too am having problems getting the self register to work. Can you
attach a sample password file?? When I click the New user, nothing
happens. I do not get the screen that shows on this demo site. |
self register enhancmenets, posted by eric wooten on Fri Aug 16 09:06:17 2002
|
Couple Wish List Items for the Self Register:
-allow the user to pick which type of log entries (which categories, etc)
they would like to subscribe to and receive notifications on.
-Option to use an existing LDAP database to authenticate users instead of
maintaining a password file. |
Re: password file and self register, posted by eric wooten on Fri Aug 16 09:32:07 2002
|
Ok I got the password file to finally work. Once I created a blank
passwd.txt I get the self register page to appear and create the account.
Next problem. Once I'm logged in, and I click logoout, I get an error
saying
the logout command now allowed ??? Same holds true for the config option
while logged in.
> I too am having problems getting the self register to work. Can you
> attach a sample password file?? When I click the New user, nothing
> happens. I do not get the screen that shows on this demo site. |
Problem with konqueror and pulldown menu (in config menu), posted by Stefan Siegel on Fri Aug 16 10:14:19 2002
|
Hi ,
currently I am running Elog 2.1.1; when using a konqueror browser (ver.
2.2.1, kde 2.2.1) the admin user cannot access in the Config menu the Login
infos for other users except himself. The pulldown menu "Select user" is
shown, but when the admin selects another user the info fields (Login name,
full name, email) are not updated. They still show the attribute values for
the admin user himself.
Is there a solution available?
Thanks (also for this very useful tool) and regards,
Stefan |
Re: self register enhancmenets, posted by eric wooten on Fri Aug 16 10:26:14 2002
|
Also having the ability to subscribe to notifications for one or more
logbooks (if access is given - along with the ability to choose which
categories, etc notifications are sent.
> Couple Wish List Items for the Self Register:
>
> -allow the user to pick which type of log entries (which categories, etc)
> they would like to subscribe to and receive notifications on.
>
> -Option to use an existing LDAP database to authenticate users instead of
> maintaining a password file. |