Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 116 of 806  Not logged in ELOG logo
ID Datedown Icon Author Author Email Category OS ELOG Version Subject
  68919   Mon Mar 25 12:31:34 2019 Question gibelin juliengibelin@unicaen.frQuestionLinux3.1.1 revision elog client through proxy

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

:

 

  68918   Fri Mar 22 11:52:46 2019 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionLinuxlatestRe: Interfaced with SSO

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

Patricia Mendez Lorenzo wrote:

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

 

  68917   Fri Mar 22 09:53:39 2019 Question Patricia Mendez Lorenzopatricia.mendez@cern.chQuestionLinuxlatestInterfaced with SSO

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

  68916   Thu Mar 21 16:14:00 2019 Question Ben Loerben.loer@pnnl.govQuestionLinux3.1.3elog.css and lock.png fail to load with top groups

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, ??

 

Attachment 1: elog1.png
elog1.png
  68915   Wed Mar 20 06:50:57 2019 Reply Ross Gibsonross.gibson@newcastle.edu.auQuestionWindows3.1.4Re: HTML editor not working after updating to V3.1.4

Thanks Stefan. Tried these without success. I tried opening in another browser and it works fine in Firefox or Internet Explorer - the problem only appears in Microsoft Edge. Perhaps its an issue with a Microsoft update (corporate rollout) to Edge and just a coincidence that I noticed it after updating Elog.


Stefan Ritt wrote:
Have you cleared your browser cache? There might be some old JavaScript stored there. If that does not help, remove elog and reinstall it to make sure to have the correct libraries on the server (first back up you logbooks, then restore them afterwards).

Stefan


Ross Gibson wrote:
Since updating to v3.1.4 the HTML editor has stopped working. If I switch to HTML encoding, the editor appears with a blank field, cannot select or type in field and none of the buttons work.
I have tried reverting to earlier versions, but the issue persists. Any suggestions to rectify?
  68914   Wed Mar 20 01:12:36 2019 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows3.1.4Re: HTML editor not working after updating to V3.1.4
Have you cleared your browser cache? There might be some old JavaScript stored there. If that does not help, remove elog and reinstall it to make sure to have the correct libraries on the server (first back up you logbooks, then restore them afterwards).

Stefan


Ross Gibson wrote:
Since updating to v3.1.4 the HTML editor has stopped working. If I switch to HTML encoding, the editor appears with a blank field, cannot select or type in field and none of the buttons work.
I have tried reverting to earlier versions, but the issue persists. Any suggestions to rectify?
  68913   Tue Mar 19 23:24:48 2019 Question Ross Gibsonross.gibson@newcastle.edu.auSince updating to verQuestionWindows3.1.4HTML editor not working after updating to V3.1.4
Since updating to v3.1.4 the HTML editor has stopped working. If I switch to HTML encoding, the editor appears with a blank field, cannot select or type in field and none of the buttons work.
I have tried reverting to earlier versions, but the issue persists. Any suggestions to rectify?
  68912   Tue Mar 19 06:13:03 2019 Question Takashi Ichiharaichihara@ribf.riken.jpQuestionLinux3.1.4 Reverse proxy setting of Elog for Apache httpd 2.4 so that changing password windows works ?

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.

ELOG V3.1.5-3fb85fa6