As the title says, we have our elog running behind an Apache proxy that is also providing authentication. We also have top groups enabled.  The first time a user views a top group page with a fresh browser cache, the index is delivered, but requests for elog.css and lock.png are returned with http 302 with location set to the elog root.  (I.e., if the server is proxied under server.example.com/logs,  the first request for server.example.com/logs/TopGroup1/elog.css returns a 302 with location set to server.example.com/logs// ). 

Any subsequent visits return the files fine. The attached screenshot shows the network requests in chrome. 

Is this a proxy configuration issue, something we've set wrong in elog, ??

Looks more like a bug to me. Will investigate.

Stefan

Dear users,

we started an elog serveur (using ssl) and open to the world which is working fine.

However I am trying to access it via the command line client, from a computer that uses a proxy to connect to internet.

The environnment variable are set :

declare -x ftp_proxy="ftp://myproxy:3128/"
declare -x http_proxy="http://myproxy:3128/"
declare -x https_proxy="https://myproxy:3128/"
declare -x socks_proxy="socks://myproxy:3128/"
 

but when I try to connect

elog  -h myelog -p 443 -l lognote -s 1 -u username passwd  -w last

I have the following message :

Cannot connect to host myelog, port 44

How should I proceed ?

Best regards

JG

:

The "elog" client does unfortunately not support proxies. You could however achieve the same with the "curl" tool. Have a look at elog:68597

Stefan

I know you can restrict access to logbooks on per user basis but can anyone tell me if it is possible to HIDE certain logbook tabs/groups on per user basis (ie, so they would just see logbooks they are authorized to see)?

In CentOS 7.6 + Apache httpd-2.4.6 + ELOG V3.1.4 environment with Reverse Proxy setting of

/etc/httpd/conf/httpd.conf
 :
ProxyRequests Off
RedirectMatch ^/elog$ /elog/
<Location /elog/>
ProxyPass                      http://mmm.riken.jp:3333/ 
ProxyPassReverse         http://mmm.riken.jp:3333/
ProxyPassReverseCookiePath   /      /elog/
</Location>
:
It almost works fine.  But Changing password has problem. 

When clicking the "Forget password?" link in login window and displaying "Entering your user name or email address"
and entering it, an email is sent to the user:

----
This is an automatically generated account recovery email for host mmmm.riken.jp.
Please click on following link to recover your account:

http://mmm.riken.jp/elog/?redir=%3Fcmd%3DChange+password%26oldpwd%3DIHCPHXNTMJGEYDKY&uname=test&upassword=IHCPHXNTMJGEYDKY

ELOG Version 3.1.4
---

Clicking the URL above in the Firefox Browser results invalid URL: 

http://mmm.riken.jp/?cmd=Change%20password&oldpwd=IHCPHXNTMJGEYDKY

These parameters does not pass to the elog by the Reverse Proxy setting above.

 While accessing the URL of (native elog port: 3333)

http://mmm.riken.jp:3333/?cmd=Change%20password&oldpwd=IHCPHXNTMJGEYDKY

displays the normal page for Changing password windows for the user.

Is there any suggestions for the Reverse Proxy setting in Apache httpd 2.4 
so that the changing password windows works fine ?

Thank you for any suggestions.

The problem was resolved. I forgot to do this statement...

https://elog.psi.ch/elog/adminguide.html
Because elogd uses links to itself (for example in the email notification and the redirection after a submit), it has to know under which URL it is running. If you run it under a proxy, you have to add the line:

    URL = http://your.proxy.host/subdir/

into elogd.cfg.

After inserting the URL in elogd.cfg, elog works correctly with Reverse Proxy Setting of Apache 2.4.

Dear Supporters,

I am evaluating the elog software as lobgook for high energy pgysics and I was just wondering the interface with SSO from the login point of view. Once euthenticated with SSO, can this authentication be also recognized by elog?

Thank you so much

Best Regards,

PAtricia

ELOG understands kerberos authentication (See https://elog.psi.ch/elog/config.html#access).

If your SSO works with kerberos, then your SSO user name and password can be used to sign in to ELOG. But I'm not sure if that is what you are asking for...

Cheers, Andreas

First, thank you so much for elog;
after using it for about 3 years, it has proven really handy and reliable.

When there is a very long URL in a message in "plain" encoding,
and this message is displayed in a list of messages,
a very long scrollbar appears at the bottom (same "scroll width" as the URL)
and some tabs and and dropdowns (filters) are unreachable without scrolling.

This does not happen if

• the message is displayed in single message page
• the message has a ELCode encoding

The exact version used is
0b9f7ed0 Merge branch 'develop'

There are no relevant instructions in elog.css for .messagelist,
and I did not find any obvious fix in the source code.

I tried to run elog with SSL so I created key and crt files. In crt file I added client certificate and intermediate certifacte. Unfortunately, when I try to run openssl s_client -showcerts -connect myexample.com:443 I got only the first certificate from the chain. Anyone has idea why this happens?