Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 433 of 808  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Version Subject
  66356   Thu May 7 13:46:37 2009 Reply Mikemike@raghuexim.comBug reportLinux2.7.6-2191Re: "Forgot Password?" link not working?

Stefan Ritt wrote:
Mike wrote:

 Thanks for the fix. I tried out 2197 and when I click the "Forgot Password" link it causes elog to crash. I've attached my cfg file.

The problem was the password recovery in conjunction with "Bottom text", thanks for supplying your configuration file. I fixed that in revision 2198.

 That did the trick, thanks for the fix!

  66355   Thu May 7 13:35:32 2009 Reply Rich Sterlingrbsterli@juno.comQuestionAll2.7.6Re: Office 2007 file attachments download as zip due to mime config

Stefan Ritt wrote:
Rich Sterling wrote:

Are there any plans to add the new mime extensions to the elogd.c source? (Instead of forcing users to use FireFox or Right click, save-as and rename?

 

 Ok, I added the MIME extensions in ELOG Rev. 2196. The forum runs already the updated version, so can you try with the demo attachments from your entry?

 It looks good from here!  Thanks!!

Best Regards,

Rich

  66354   Thu May 7 08:05:54 2009 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.7.6-2191Re: "Forgot Password?" link not working?
Mike wrote:

 Thanks for the fix. I tried out 2197 and when I click the "Forgot Password" link it causes elog to crash. I've attached my cfg file.

The problem was the password recovery in conjunction with "Bottom text", thanks for supplying your configuration file. I fixed that in revision 2198.

  66353   Wed May 6 20:49:24 2009 Question Alexander Withersalexw@bnl.govQuestionLinux2.7.5-2130help with substituting subjects

I am trying to add additional information to the subject of new entries:

Subst subject = $subject [INCIDENT $message id]
Subst on reply subject = Re: $subject
Fixed Attributes Reply = Subject

However, the new entry subject looks like:

this is my subject [INCIDENT this is my subject [INCIDENT $message id]

I'm not sure if there's a problem with the substitution or if this is just not allowed (I'm having LISP flashbacks).

By the way, if I use "Subst on reply subject" I get the behavior I would like but the original entry in the thread doesn't contain the appended data:

Subst on reply subject = Re: $subject [INCIDENT $message id]

Any help would be appreciated.

Alex

  66352   Wed May 6 18:31:19 2009 Reply Mikemike@raghuexim.comBug reportLinux2.7.6-2191Re: "Forgot Password?" link not working?

Stefan Ritt wrote:

 

Mike wrote:

I have my site running under apache. I don't have a /elog/ directory.

for example most would do http://www.example.com/elog/ to visit elog

but my site loads at http://www.example.com/

The site is private so it's password protected. Everything works fine except

if I click the "Forgot Password" link it does nothing.

but if I go to one of the log books...

http://www.example.com/open/

The forgot password link works.

Is there anyway to fix this? I have nothing else running on the server, it's dedicated to only ELOG.

That's why I don't want to have it running under /elog/ in the url.

 

Thanks for reporting this bug, I fixed it in revision 2197 which you can load from the SVN server.

Thanks for the fix. I tried out 2197 and when I click the "Forgot Password" link it causes elog to crash. I've attached my cfg file.

 

  66351   Wed May 6 16:03:56 2009 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.7.5Re: Multi Logook Login

Yoshio Imai wrote:
Hi, Stefan!


Stefan Ritt wrote:
If "password file = xxx" is however in each individual logbooks configuration, then you get "path=/<lobook>". You can check that by inspecting your browser's cookies. In that case the login name and password cookies are only sent to the URL for that specific logbook. I have not tested that extensively (different browsers, with/without Apache proxy), but if it works reliably, I will put this into the documentation.


We had done so on your advice and in principle this works, but our experience has shown one problem:

We have separated our logbooks into different top groups because of the sheer number of them (i.e. experiment logbooks in one top group with logbook groups for the sub-categories, personal analysis logbooks in another top group etc.). Obviously, the experiment logbooks may share the same login, therefore we have put the "password file" statement into that top group's global section (otherwise, we would have to log on to every beamtime logbook individually, which can be cumbersome when comparing e.g. experiment settings between beamtimes). For the personal logbooks, of course, we use per-logbook-access (i.e. "password file" statement in the individual logbook sections) such that logging on to one's own logbook does not imply access to someone else's logbook. However, since the group/top group structure does not appear in the elog URLs, the cookies for the beamtime logbooks all have the path set to "path=/". This breaks the scheme again (I guess we have sort of "abused" the concept of top groups a little) and it is not possible to work in one of the experiment logbooks in parallel with one's own logbook without having to renew the login when switching the logbook.


Is it possible to modify the elogd such that it first checks if, among the cookies sent, there is one where the path corresponds to the path of the current logbook, and evaluate cookies with "path=/" only if no such cookie is found?

Yoshio


I'm not sure if that helps. As soon as you have top groups, cookies have to use "path=/". I agree it would be best to use URLs in the form "http://<server>/<top group>/<logbook>", but cookies only support one level of directories (at least that was the case when I designed that a few years ago, I'm not sure if that's still the case). The only way around that is to give up top groups and run one elog server for each top group on a different port.
  66350   Wed May 6 15:56:10 2009 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.7.6-2191Re: "Forgot Password?" link not working?

 

Mike wrote:

I have my site running under apache. I don't have a /elog/ directory.

for example most would do http://www.example.com/elog/ to visit elog

but my site loads at http://www.example.com/

The site is private so it's password protected. Everything works fine except

if I click the "Forgot Password" link it does nothing.

but if I go to one of the log books...

http://www.example.com/open/

The forgot password link works.

Is there anyway to fix this? I have nothing else running on the server, it's dedicated to only ELOG.

That's why I don't want to have it running under /elog/ in the url.

 

Thanks for reporting this bug, I fixed it in revision 2197 which you can load from the SVN server.

  66349   Wed May 6 15:38:10 2009 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.7.5-2130Re: Mirror Server Funktion

 

Andreas Wilke wrote:

Ich möchte meine "lokale" ELOG Installation mit einem Server in der Firma synchronisieren.

Dazu habe ich in der entfernten Firewall ein Portmapping auf den ELOG Server in der Firma eingerichtet.

Wenn ich von meiner "lokalen" Maschine im Browser  http://meinedomain.dyndns.xx:PORT aufrufe, kann ich auf den ELOG Server zugreifen.

Ich habe in meiner "lokalen" Installation in der Section [global] den Mirror-Server = http://meinedomain.dyndns.xx:PORT angeben.

Beim Synchornisieren bekomme ich jedoch den Hinweis "Fehler beim Zugriff auf entfertes Logbuch".......

 

Please let's stick to English. Let me try to understand your configuration. You have one elog server running and want to synchronize with itself? That does not work of course, synchronizing is done between two servers (normally on different computers).

ELOG V3.1.5-3fb85fa6