Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 638 of 808  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
    icon2.gif   Re: Allow password change ???, posted by Stefan Ritt on Tue Apr 14 08:48:24 2009 

 

Hal Proctor wrote:

 

Hal Proctor wrote:

How do you allow users to change password for a given logbook when the user keeps getting prompted for admin password to enter the change password feature?

I have Allow password change = 1 set global and at each logbook hoping that would work.

It allows them to change the password when and only when the user gets past the admin login when clicking CONFIG.

help

 

 

 Thats what we get for having two people working on the install and configuration.  LOL

When first creating and setting up the configs, we had  Admin Password = xxxxx  entered in each logbook config.  Once we created a password list we no longer needed that entry.

This was why each user who had login credentials was being asked to provide the admin password when trying to change their password. 

 

I didn't get your point completely, so is this issue now resolved? 

    icon2.gif   Re: Allow $attributes in "Comment = " option, posted by Stefan Ritt on Mon Mar 6 13:40:40 2006 

Steve Jones wrote:
Is it possible to allow $attribute substitutions in the "Comment =" option for logbooks?


The "Comment =" option for logbooks gives a general comment, like Discussion forum about ELOG for this forum. Since this comment is global, it does not make sense to have $attribute substitution.
    icon2.gif   Re: Allow $attributes in "Comment = " option, posted by Steve Jones on Mon Mar 6 17:43:11 2006 

Stefan Ritt wrote:

Steve Jones wrote:
Is it possible to allow $attribute substitutions in the "Comment =" option for logbooks?


The "Comment =" option for logbooks gives a general comment, like Discussion forum about ELOG for this forum. Since this comment is global, it does not make sense to have $attribute substitution.



Quote:
Ok, just a thought. Thanks
    icon2.gif   Re: Admin rights lost after upgrade 2.5.2 to 2.5.4, posted by Stefan Ritt on Wed Sep 8 12:25:20 2004 
> Somehow elogd 2.5.4 treat all users as normal user. When clicking on
> "config". All admin users has no "change elogd.cfg" button. Revert back to
> 2.5.2 OK.
> 
> Is there anything I need to change to upgrade other than replaceing elogd?
> Clearing the cookies didn't help.

The button name has been changed from "change elogd.cfg" to "change config file"
since the file name is now variable (can be changed during compile time). But I
guess this is not your problem.

Can you try with the demo logbook (contained in the distribution). Just add
"password file = ..." and "admin user = ..." to the sample elogd.cfg. If I do that
here, everything works fine. You also can send me your elogd.cfg so I can have a look.
    icon2.gif   Re: Admin right, posted by Stefan Ritt on Fri Jul 9 10:32:52 2004 
> I have setup top group in my elog . I will want to restrict the different 
> admin user on the global and the global on top groups .
> But however i am not able to use the configuration on "admin user" on the 
> global portion to strict admin of top group to access the main global 
> config .
> Did i configure it wrongly or is there a way?

There was indeed a bug which I fixed. Please obtain the newest snapshot (see
download page). If an admin user is defined in a top group, it does not gain
access to the global if the admin of the global is different, like

[gloabl]
password file = passwd
admin user = joe

Top group g1 = demo1, demo2
Top group g2 = demo3, demo4

[global g1]
admin user = joe

[gloabl g2]
admin user = jack

[demo1]
....

So if user "jack" is logged in to demo3 and therefore g2, he can change the
[global g2] section, but not the [global] section, since only user "joe" is
allowed to so do.

> And for email notification , is there a way which i can select who to email 
> it to ? like check box etc.

This is not directly implemented, but one can configure this kind of "manually",
like

Attributes = ..., Send Email, ...
ROptions Send Email = joe, jack, ...

Email "Send email" joe = joe@some.domain
Email "Send email" jack = jack@other.domain

The option "Email <attribute> <value> = <email address>" gets executed when the
attribute "Send email" has the value "joe" in the first line, so email is sent
to joe@some.domain. It's a bit cumbersome since one cannot use the email
addresses from the password file, but better than nothing. 

> And is there a way which i can setup the summary page to refresh every 
> 15mins , so that new entry can be shown ?

No, this is not foreseen. One should use email notification for that, which
tells you immediately (not after 15 mins) when a new entry has been submitted.

> And can i make the message id unique , when i move the messages from one 
> log book to another log book , the messages id change accorddingly based on 
> the number or messages . Anyway for me to make it fixed even i moved to 
> another log book , i need the running number still .

The message id must be unique in a logbook (like in a relational database). If I
would keep the id when moving entries to another logbook, this could cause a
conflict. Assume you have two logbooks both with three entries having ID's
1,2,3. Now you move ID 3 from the first logbook to the second, but ID 3 exists
already in the second logbook, so you would have that ID twice, which breaks the
database structure. What you can do however is user an "numbered" attribute like

Attributes = ..., tag, ...
Preset tag = ID%d

For each new submission, the attribute "tag" gets a new number, like ID1, ID2
etc. These attributes are not modified when moving an entry to another logbook,
but if the target logbook has already an entry with the same tag, you get this
tag twice. I don't know if that is what you want...
    icon2.gif   Re: Admin right, posted by Geo Geo on Wed Jul 14 13:55:13 2004 
Hi Stefan
Thanks for your reply
Can i check , with the new snap shot , can i disable the capability for the admin 
to delete the logbook and create new logbook
I tried with the config -
Allow Delete the logbook = admin 
 but cannot , please advise

And As for the id , can i have the month and the day in the id , what is the 
corresponding field for just the month and day , if there is .

And is there a way to prevent preset value get overwritten when user do a reply
Example , i preset a field with 
Preset test = "9v"
so when the user submit , it will have 9v and they may have enter some following 
value. but when a user reply , the test field get reset back to 9v

Thanks 


> > I have setup top group in my elog . I will want to restrict the different 
> > admin user on the global and the global on top groups .
> > But however i am not able to use the configuration on "admin user" on the 
> > global portion to strict admin of top group to access the main global 
> > config .
> > Did i configure it wrongly or is there a way?
> 
> There was indeed a bug which I fixed. Please obtain the newest snapshot (see
> download page). If an admin user is defined in a top group, it does not gain
> access to the global if the admin of the global is different, like
> 
> [gloabl]
> password file = passwd
> admin user = joe
> 
> Top group g1 = demo1, demo2
> Top group g2 = demo3, demo4
> 
> [global g1]
> admin user = joe
> 
> [gloabl g2]
> admin user = jack
> 
> [demo1]
> ....
> 
> So if user "jack" is logged in to demo3 and therefore g2, he can change the
> [global g2] section, but not the [global] section, since only user "joe" is
> allowed to so do.
> 
> > And for email notification , is there a way which i can select who to email 
> > it to ? like check box etc.
> 
> This is not directly implemented, but one can configure this kind of "manually",
> like
> 
> Attributes = ..., Send Email, ...
> ROptions Send Email = joe, jack, ...
> 
> Email "Send email" joe = joe@some.domain
> Email "Send email" jack = jack@other.domain
> 
> The option "Email <attribute> <value> = <email address>" gets executed when the
> attribute "Send email" has the value "joe" in the first line, so email is sent
> to joe@some.domain. It's a bit cumbersome since one cannot use the email
> addresses from the password file, but better than nothing. 
> 
> > And is there a way which i can setup the summary page to refresh every 
> > 15mins , so that new entry can be shown ?
> 
> No, this is not foreseen. One should use email notification for that, which
> tells you immediately (not after 15 mins) when a new entry has been submitted.
> 
> > And can i make the message id unique , when i move the messages from one 
> > log book to another log book , the messages id change accorddingly based on 
> > the number or messages . Anyway for me to make it fixed even i moved to 
> > another log book , i need the running number still .
> 
> The message id must be unique in a logbook (like in a relational database). If I
> would keep the id when moving entries to another logbook, this could cause a
> conflict. Assume you have two logbooks both with three entries having ID's
> 1,2,3. Now you move ID 3 from the first logbook to the second, but ID 3 exists
> already in the second logbook, so you would have that ID twice, which breaks the
> database structure. What you can do however is user an "numbered" attribute like
> 
> Attributes = ..., tag, ...
> Preset tag = ID%d
> 
> For each new submission, the attribute "tag" gets a new number, like ID1, ID2
> etc. These attributes are not modified when moving an entry to another logbook,
> but if the target logbook has already an entry with the same tag, you get this
> tag twice. I don't know if that is what you want...
    icon2.gif   Re: Admin right, posted by Stefan Ritt on Wed Jul 14 16:26:48 2004 
> Can i check , with the new snap shot , can i disable the capability for the admin 
> to delete the logbook and create new logbook
> I tried with the config -
> Allow Delete the logbook = admin 
>  but cannot , please advise

No, disabling the capability to delete the logbook is not implemented. Usually the
admin user is an experienced user who knows what she/he does. The admin user typically
also was write access directly to the elogd.cfg file, and no flag in the world can
then prevent them from adding/removing logbooks by changing elogd.cf directly.

> And As for the id , can i have the month and the day in the id , what is the 
> corresponding field for just the month and day , if there is .

No, but it's on the wishlist. I added your vote there.

> And is there a way to prevent preset value get overwritten when user do a reply
> Example , i preset a field with 
> Preset test = "9v"
> so when the user submit , it will have 9v and they may have enter some following 
> value. but when a user reply , the test field get reset back to 9v

This is clearly a bug. The 'Preset test = 9v' should not be evaluated on a reply. I
fixed that and updated the CVS and snapshot.

- Stefan
    icon2.gif   Re: Admin password, posted by Stefan Ritt on Mon Jul 1 10:36:47 2002 
> I want to set up eLogs for a class w/out the need for passwords. But, at the
> same time, I don't want the students to change the config file. I tried
> setting up a global password, but am having some difficulty with the syntax
> I suppose I could remove the config command from the menu and edit the file
> using Pico, but that would require a better memory than I have...
> 
> ******************
> 
> usage: elogd [-p port] [-h hostname] [-D] [-c file] [-r pwd] [-w pwd] [-a
> pwd] [-l logbook]
> 
>        -p <port> TCP/IP port
>        -h <hostname> TCP/IP hostname
>        -D become a daemon
>        -c <file> specify configuration file
>        -v debugging output
>        -r create/overwrite read password in config file
>        -w create/overwrite write password in config file
>        -a create/overwrite admin password in config file
>        -l <logbook> specify logbook for -r and -w commands
> 
>        -k do not use keep-alive
> 
> [root@eMonster elog]# elogd -a youtheman
>           
> Must specify a lookbook via the -l parameter.

Nearly correct, just follow the note: specify a logbook via the -l parameter.
So if you logbook is called "linux", you enter

elogd -a youtheman -l linux
ELOG V3.1.5-3fb85fa6