Looking at some of the questions here this seems too newbie to even ask.

I want to set up a log book for my mechanics. I want them to each have a password to log in and enter what they do each day.

When I try to set up a password file it takes all the info, then when I hit save it says "server has been reset" and it will not log in. I have to remove the password = and restart the server.

[global]
port = 8080


[TFB]
Password file = <tfbpass>


Theme = default
Comment = TFB ENGINEERING
Attributes = Mechanic, Type of entry, Status, Subject
Attributes = Author, Status
Options Status = Completed, Incomplete, Notification only
Cell Style Status Completed  = background-color:green
Cell Style Status Incomplete  = background-color:red
Cell Style Status Notification only  = background-color:yellow



Options Mechanic= Jeff K, Arnaldo M, Bob L, Nathan P
Options Type of entry = Break Down, PM Repair, Building, FYI, Other
Options Status = Completed, Incomplete, Notification only, Other
Extendable Options = Category, Status,
Required Attributes = Mechanic, Type of entry, Category, Status,
Page Title = TFB Engineering - $subject
Reverse sort = 1
Quick filter = Date, Mechanic

 

Some options for the password setting:
The ability that if admin creates a temporary password for the user, force 
the user to change the password once logged in.

User forgets password, system generates a random pwd and sends it to user 
via email, after they log in force pwd change. 

option to expire an account or expire a pwd after so many days??

just some ideas..

still loving the new features!!

 I'm trying to use gmail to send password recovery e-mails, I get this error when I submit the email address.

"Error sending Email via "smtp.gmail.com": 5.7.0 Must issue a STARTTLS command first. 2sm5111524agd.34"

Any help or insight would be appreciated.

Ed... 

Hi.

I have ELOG V2.8.0-2313 installed on a SLC 5.5 release and all works fine, Users can register them-self and I see for each of them in the passwd file:

<name>test</name>

<password>***something***</password>

....

after a '/etc/rc.d/init.d/elogd restart' the logins don't work anymore (they did before the restart)

and the passwd file changed:

<name>test</name>

<password encoding="SHA256">***something else***</password>

....

Any idea what goes wrong?

Cheers, Jack

After setting up email addresses for notifications I noticed that the "Full Name" has part of an email address in it. I've tried several ways to correct this however it keeps sending me to a page that says "Password may not contain blanks" and I've not done anything with the password.

Can you tell me how to correct this issue?

I certainly appreciate your help!!

Terry

We don't use a password file but would like to password protect (Admin only) the DELETE function in the MENU     Thank You

I noticed that when I put in a password such as <test1> a person can login 
with the password <test2> or any other number at the end.  Is the 
encryption not able to tell the difference between numbers?  The encrypted 
passwords even look the same in the password file.  Is this a bug?

I expanded an elog server from 1 to 3 logbooks. For each logbook there is a separate password file defined. 

When I try to add a new user in one of the 2 new logbooks using config => new user, it adds the user to the password file for the original logbook.

Have verified that access to the logbooks is controlled via the separate password files. If it would help to provide an example of the elogd.cfg or if I need to clarify further, let me know. 

Any suggestions welcome.

Thanks. Mark.