Hello, my sending of emails was working a while back but I have not checked on it in a few months and found out I am getting authentication errors sending to my MTA (mailer). I was using a base64 to encode the pw but now my mailer (gandi.net) rejects it. Has anything changed over the last couple of years with Elogs code that would be affecting this? I just upgraded (Linux) and changed my testing grounds to non-production and the same problem exists. Thing is I CAN send using other programs, but not with Elog. It is impertive I figure this out or have a work around.. but a 'work around' does not seem like a possible  task since all the work (forums and such) will be via my Elog server.

Thanx, John

Good morning,

I would like to ask you whether it is feasible to establish a logbook that limits access to entries, enabling each user to view only their own.
Although creating a logbook per user is an apparent solution, it does not meet my requirements.

Thank you in advance.

Leonardo

Hello

I was wondering if there is any possibility to let the user decide which columns to show/download in the search results? We have quite a lot of fields and it would help the usefulness of our elog a lot.
(If there is an obvious possibility that I missed I'm sorry).

Thanks a lot!

Hi all,

I am using the Apache webserver authentication and redirection over http (not https). I have configured it 1:1 as described in the Adminguide. In the elog.cfg I set Authentication = Webserver.

All works fine; the webserver requests an authentication and elog recognizes me correctly.
However, when I close and reopen the browser and log in as a different user, elog does not change the user (tested with Firefox and Edge).
I can only change the user if I use a different browser or restart the elogd (reload is not enough).
The X-Forwarded-User header is set to the correct username - I have checked it with a CustomLog in Apache.

Best regards,
Frank

I am running elog under Apache as explained in the administrator's guide. Everything works fine, butmy IT service complains about the elog port being publicly exposed, so I have to fix this. As far as I understand when running under a reverse proxy there's no need for the port to be publiuclyexposed, but I cannot find how to configure the elog server to expose it only locally

Hi there. I have been testing a set-up of elog behind an Apache reverse proxy using the Webserver auth method. Apache has been configured for LDAPS with Active Directory allowing us to restrict Elogs by AD group, something not able to be done with the LDAP module.

Testing with Elog 3.1.4 (on Windows) and also Elog 3.1.5 (compiled on Ubuntu 20.04) I experience an issue that when the user logs in for the first time using the above they get the self registration box asking for name and email, and then once they hit save they get an error that says: "Error: Command "Config" not allowed".  Once the error is dismissed it never comes back, but its confusing for users who call for help when they first see it.

Is there a way to skip the self registration with the Webserver auth method? and if not is there a reason for the error?

Attached is a copy of the error and an elog config file. Any ideas?

PS. As a side piece the logout options for Webserver needs some enhancement, maybe an option to close the web browser or tab so that it does not retain the logged in cookies.

Hi,

As there is no ELOG available in Epel repository for Rocky9, I tried to install ELOG from https://elog.psi.ch/elog/download/RPMS/elog-latest.el7.x86_64.rpm and ended with the below error in Rocky 9.

=======================================
[root@test.com]# wget https://elog.psi.ch/elog/download/RPMS/elog-latest.el7.x86_64.rpm
--2024-02-20 10:11:32--  https://elog.psi.ch/elog/download/RPMS/elog-latest.el7.x86_64.rpm
Resolving elog.psi.ch (elog.psi.ch)... 192.33.120.112
Connecting to elog.psi.ch (elog.psi.ch)|192.33.120.112|:443... connected.
ERROR: The certificate of ‘elog.psi.ch’ is not trusted.
ERROR: The certificate of ‘elog.psi.ch’ doesn't have a known issuer.
=======================================

Could someone guide me on how to install Elog in Rocky 9 securely? 

Hi,

As there is no ELOG available in Epel repository for Rocky9, I tried to install ELOG from https://elog.psi.ch/elog/download/RPMS/elog-latest.el7.x86_64.rpm and ended with the below error in Rocky 9.

=======================================
[root@test.com]# wget https://elog.psi.ch/elog/download/RPMS/elog-latest.el7.x86_64.rpm
--2024-02-20 10:11:32--  https://elog.psi.ch/elog/download/RPMS/elog-latest.el7.x86_64.rpm
Resolving elog.psi.ch (elog.psi.ch)... 192.33.120.112
Connecting to elog.psi.ch (elog.psi.ch)|192.33.120.112|:443... connected.
ERROR: The certificate of ‘elog.psi.ch’ is not trusted.
ERROR: The certificate of ‘elog.psi.ch’ doesn't have a known issuer.
=======================================

Could someone guide me on how to install Elog in Rocky 9 securely?