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. |
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. |
|
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: 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 |
|
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 |
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 |
|
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 |
|
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 |