user change under webserver authentication not recognized, posted by Frank Heyroth on Fri Jan 19 15:49:13 2024
|
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. |
Re: user change under webserver authentication not recognized, posted by Frank Heyroth on Wed Jan 24 14:50:21 2024
|
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: |
|
Re: user change under webserver authentication not recognized, posted by Stefan Ritt on Fri Feb 23 15:13:46 2024
|
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
Frank |
http status 200 returned for "file not found", posted by Konstantin Olchanski on Fri Mar 18 00:36:37 2022
|
"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
|
|
Re: http status 200 returned for "file not found", posted by Alexey Khudyakov on Tue Jan 30 13:10:38 2024
|
> "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
|
|
Re: http status 200 returned for "file not found", posted by Stefan Ritt on Fri Feb 23 14:59:29 2024
|
> > "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
|
|
ERROR: The certificate of ‘elog.psi.ch’ doesn't have a known issuer, posted by scott on Tue Feb 20 11:49:19 2024
|
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 |
|
Re: ERROR: The certificate of ‘elog.psi.ch’ doesn't have a known issuer, posted by Laurent Jean-Rigaud on Tue Feb 20 11:56:14 2024
|
Hi
You can use an option to wget to discard certificate checks m.
Btw this rpm file is build for el7 gen aka entreprise linux 7. So it souldn't install on gen 9.... |
|
Re: ERROR: The certificate of ‘elog.psi.ch’ doesn't have a known issuer, posted by Konstantin Olchanski on Wed Feb 21 00:12:45 2024
|
> wget https://elog.psi.ch/elog/download/RPMS/elog-latest.el7.x86_64.rpm
I confirm, both wget and curl do not work, not happy with https certificate. (current macos)
|
Re: ERROR: The certificate of ‘elog.psi.ch’ doesn't have a known issuer, posted by Laurent Jean-Rigaud on Wed Feb 21 03:13:33 2024 
|
To have ELOG RPM for EL9, you need to rebuild package from source under EL9 host or VM (i use almalinux9 for this test) :
1- install RPM build tools (csh is used by ELOG scripts. Devel rpms are dependencies) :
sudo dnf install rpm-build gcc gcc-c++ git openssl-devel krb5-devel pam-devel openldap-devel csh
2- retrieve last source |
|
Re: ERROR: The certificate of ‘elog.psi.ch’ doesn't have a known issuer, posted by Stefan Ritt on Wed Feb 21 09:16:00 2024
|
The chain certificate on elog.psi.ch has been expired, so I installed the current one and now wget should be happy ;-)
Stefan
scott |
|
ERROR: The certificate of ‘elog.psi.ch’ doesn't have a known issuer, posted by scott on Tue Feb 20 11:44:30 2024
|
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 |
|
Webserver Auth Method and Self Registration, posted by James on Sun Feb 18 11:43:07 2024
|
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 |
|
How to not expose elog port when running under a reverse proxy, posted by Nicola on Mon Jan 22 08:22:33 2024
|
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 |
|
Re: How to not expose elog port when running under a reverse proxy, posted by Frank Heyroth on Mon Jan 22 20:50:50 2024
|
Hi,
as I understand right you can do this in the elogd.cfg via
Interface = 127.0.0.1 |
|
Let the user decide which columns should be displayed, posted by Sarah Kuckuk on Thu Jan 18 13:56:59 2024
|
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. |
|
Re: Let the user decide which columns should be displayed, posted by Stefan Ritt on Mon Jan 22 12:15:26 2024
|
There is a general display option "List display", but that applies for all users. For the download, you can load the CSV file into a spreadsheet
program and then delete some columns.
Stefan |
Maximum number of attributes, posted by Dr Marta Divall on Mon Jan 8 11:06:49 2024
|
The maximum number or attributes is 100.
Is it possible to increase this?
Thanks! |
|
Re: Maximum number of attributes, posted by Stefan Ritt on Mon Jan 8 11:08:14 2024
|
You would have to change the elogd.c code and recompile. At some point you wlll however get crash of elogd with a stack overflow. If you need more than
100 attributes, it becomes anyhow hard to manage, so I would suggest other ways, like adding iformation to the text body etc.
Best, |
|
Re: Maximum number of attributes, posted by Dr Marta Divall on Mon Jan 8 11:42:08 2024
|
Dear Stefan,
Thansk for the super fast response! To keep the stability of the system we will look for a different solution then.
Best, |
|
Re: Maximum number of attributes, posted by David Pilgram on Mon Jan 8 15:56:40 2024
|
In my case, I had a number of attributes which had a varied prefix. For example, "progressed" , which could have no prefix, or prefix
"I", "To be", "Strongly", "Seriously"... and that was true (the same prefixes, or at least many of them) for a
number of attributes. Splitting them into two groups, the prefixes and the action, allowed me to gain more actual attributes without having to recompile. |
|
Re: Maximum number of attributes, posted by Dr Marta Divall on Mon Jan 8 16:18:45 2024
|
To explain the problem, we have silicon chip designs, which we log with an indentifyier, which is the attribute for easy search, as we want to follow
their progress from design thorugh fabrication to testing, involving many people. They are called D_001; D_099...you get it. We have reached the 100, but
maybe it is the est just to create an archive after each 100 design and make a new tab/logbook. Any other suggestions are of course welcome. |
|
Re: Maximum number of attributes, posted by Stefan Ritt on Mon Jan 8 16:25:05 2024
|
Why don't you simply create a single attribute "identifier", which then gets a value D_001, ..., D_xxx. You can still use the D_xxx in
full text search.
Stefan |
|
Re: Maximum number of attributes, posted by David Pilgram on Mon Jan 8 17:30:42 2024
|
Or what about the "ticket number" feature? Every new entry thread (sorry, confusing terminology on my part) would
increment the ticket number by one, and there is no limit as far as I am aware. This is all explained in the elogd configuration documentation.
Stefan |
|
Re: Maximum number of attributes, posted by David Pilgram on Mon Jan 8 21:08:43 2024
|
As for my suggestion earlier, now I'm at my computer with working elog. I think that the following four lines (three I guess already there but need
alteration for this) need to appear in your elogd.conf file. The first three should also include any other thing you need to display etc. I've
cut this down to the bear bones, and ... means anything else you want to add. |