I found the reason of the bug:
In line 27441 of elogd.cxx the http_user is overwritten by the user saved in the sid_ array as a sideeffect of the sid_check function:
sid_check(getparam("sid"), http_user)

It can solved by changing elogd.cxx @ line 27441

27441c27441,27446
<          if (!sid_check(getparam("sid"), http_user)) { /*  if we don't have a sid yet, set it */
---
>          i=sid_check(getparam("sid"), thumb_name);
>          if (i && strcmp(http_user,thumb_name)!=0) {  /* user changed */
>             sid_remove(getparam("sid"));
>             i=FALSE;
>          }
>          if (!i) { /*  if we don't have a sid yet, set it */

Remark: I have used the variables i & thumb_name of the function in a local context.

> "file not found" should return http code 404. elogd returns code 200 together
> with a page containing text "404 not found". This pollutes the browser cache
> with wrong content (in this case, we are trying to load a css file, and the browser
> is trying to use text "404 not found" as if it were a css. bad. file not found
> should return http code 404. K.O.

Yes. That's quite a problem when interacting with ELOG programmatically. Only way to 
find whether response succeeded or failed with 404 is to parse response body

When file is not found send_file_direct calls show_html_header which in turn calls 
show_http_header which sets HTTP code 200 unconditionally. It's reasonably easy to 
patch around.

> > "file not found" should return http code 404. elogd returns code 200 together
> > with a page containing text "404 not found". This pollutes the browser cache
> > with wrong content (in this case, we are trying to load a css file, and the browser
> > is trying to use text "404 not found" as if it were a css. bad. file not found
> > should return http code 404. K.O.
> 
> Yes. That's quite a problem when interacting with ELOG programmatically. Only way to 
> find whether response succeeded or failed with 404 is to parse response body
> 
> When file is not found send_file_direct calls show_html_header which in turn calls 
> show_http_header which sets HTTP code 200 unconditionally. It's reasonably easy to 
> patch around.

I fixed the code to properly return "404 Not Found" in case a non-existing file is requested.

Stefan

Thanks for the fix, I committed it. Please give it a quicky try sinc I cannot test it here (don't use webserver authentication...)

Stefan

Hi Team,

Current configuration

=================

OS: Ubuntu 22.04.4 LTS

ELOG version: elog/jammy,now 3.1.3-1-1build2 amd64 [installed]

Installation method: apt install elog

Configuration file: /etc/elogd.cfg

LOGBOOKDIR= /var/lib/elog/logbooks}
RESOURCEDIR= /usr/share/elog

I had an ELOG server set up in the Windows server which is authenticated using a Password file. Recently, I have migrated the ELOG server to the Ubuntu server. I installed ELOG from the Ubuntu repository (apt install elog) and copied over the logbook and configuration file from the windows server to the new Ubuntu server. In the server, the configuration file was set to /etc/elog.conf by default. I have modified the init file and set the configuration file to /etc/elogd.cfg (this conf file is copied from the Windows server) which includes all the settings. After moving to the Ubuntu server I would like to authenticate users using the password file and LDAP. Could someone help me how to configure LDAP in my installation style?

The global configuration that is found on my installation is as follows:

###################################

; Global settings

Password file = elog.pwd
Self register = 1
Admin user = a, b,c, d, e, Iafdsel

Suppress Email to users = 1
SMTP host = example.com

Time format = %Y-%m-%dT%H:%M:%S
Date format = %Y-%m-%d

Restrict edit time = 2
Restrict edit = 1

Allow HTML = 1
Max content length = 209715200
Save drafts = 0
###################################

Should I add the below modification (by editing the necessary fields) to the current configuration? Will that make the LDAP and normal password file work?

############################

• Enable LDAP authentication in the Makefile by setting USE_LDAP = 1   (I am not sure if I need to do this in my installation style. If yes, how do i do this?)

• Authentication = LDAP
• LDAP server = ldap://example.org:389
• LDAP userbase = ou=People;dc=example,dc=org
• LDAP login attribute = uid
• LDAP register = 1

​############################
 

Can someone guide me on what changes I need to make for this?

Many Thanks,
Scott

Hello,

I've noticed that many times, I start an elog and continue editing adding to a few hours later, then I submit and it deletes everything I entered after the last time a draft was saved. I paid more attention and saw that it saves a draft after about a few minutes, and if I wait too long before submitting, it doesn't let me re-save the draft. My workaround is to copy all text before I submit, so if it ignores whatever I entered after the last saved version, I can edit it and paste it back in. Is there a setting someplace that I can change to fix this problem?

Thanks!

Hi Stefano,

I also tried to set up LDAP authentication and password file-based authentication using the same settings as yours, which is not working as expected. It does work only with the LDAP authentication and not with the password file now. If I remove the LDAP-based parameters from the configuration file it works then password files start working.

I think multiple ways of authentication do not work concurrently.


Is that issue still existing for you or is it resolved?

Thanks,
Scott


----

> Dear experts,
>    I have a logbook which has authentication as follow
> 
> Authentication = LDAP, File
> Password file = PASSWD.file
> LDAP server = ldaps://it-ldap-XXX.XXX.XX:1636
> LDAP userbase = ou=people,ou=RGY,o=XXX,c=XX
> LDAP login attribute = uid
> LDAP register = 0
> Self register = 0
> Allow password change = 0
> 
> Some of the my user (but not all) have issue in accessing this protected elogbook.
> The ldap password is correct (we checked).
> What I see in the log is as follow:
> 
> 22-Feb-2021 11:25:51 [XXX.YYY.ZZZ.QQ] {Beam Run} LOGIN user "USERNAME" (attempt)
> 22-Feb-2021 11:25:59 [XXX.YYY.ZZZ.QQ] {Beam Run} LOGIN user "USERNAME" (attempt)
> 
> The user USERNAME is present in PASSWD.file.
> 
> For other user, for which the login works, I do see an (attempt) and then (success)
> 
> we tried the standard stuff: clear cache/cookies and with different browser. We also tried to remove the user from PASSWD.file and 
> create it again, but nothing has worked.
> 
> Any suggestion how I can debug this problem?
> 
> Thanks in advance,
>   Stefano

Hello all,

I am installing elog on an Rocky Linux instance. Have dependensy problem. 

rpm -Uvh elog-latest.el7.x86_64.rpm 

error: Failed dependencies:

    liblber-2.4.so.2()(64bit) is needed by elog-3.1.5-1.el7.x86_64

    libldap-2.4.so.2()(64bit) is needed by elog-3.1.5-1.el7.x86_64

    libssl.so.10()(64bit) is needed by elog-3.1.5-1.el7.x86_64

    libssl.so.10(libssl.so.10)(64bit) is needed by elog-3.1.5-1.el7.x86_64

Any clues from developers to resolve it and keep the software working. Thank you in advance!

Bests, Nina