ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 714 of 808

Not logged in

Find | Login | Help

Full | Summary | Threaded | Hide attachments

6457 Entries

Goto page Previous 1, 2, 3 ... 713, 714, 715 ... 806, 807, 808 Next

Wed Apr 15 04:02:41 2015

Re: ELOG Version 3.1.0 announcement

congrats, any detail changelog? I assume in software packages?

is it save just install and overwrite the old version?

Stefan Ritt wrote:

This is an announcement for the ELOG version 3.1.0 being released just now. Among several bug fixes and an improved Drag & Drop interface for attachments, it contains a long awaited "autosave" feature.

Let's assume that you write an ELOG entry, and keep the window open for a longer time (like to write some shift notes over several hours). If your browser crashes or closes for some reason, you will loose your entered text. To avoid that, ELOG starting from version 3.1.0 has an autosave feature. Whenever you enter some text, it is saved in the background as a draft message to the server. If your browser is closed by accident, you always can go back to the logbook, click "New" and ELOG will tell you that there is a draft message and asks you if you want to edit it. When you edit and regularly submit this message, it becomes a "normal" entry and the draft flas is removed. In addition to the background saving, there is now also a "Save" button so you can manually save your text to the draft entry.

I have tested this to some extent, but I might not have seen all browser/OS combinations, so in case there is a problem, please report it here.

Happy Easter,
Stefan

67861

Wed Apr 15 09:01:04 2015

Re: ELOG Version 3.1.0 announcement

The changelog is here: http://midas.psi.ch/elog/download/ChangeLog

It is save to install the new version over the old one.

Banata Wachid Ridwan wrote:

congrats, any detail changelog? I assume in software packages?

is it save just install and overwrite the old version?

Stefan Ritt wrote:

I have tested this to some extent, but I might not have seen all browser/OS combinations, so in case there is a problem, please report it here.

Happy Easter,
Stefan

67882

Wed May 6 11:00:14 2015

logout to external page

Hi Stefan,

I am happy to see that you include the webserver authentication.
So I can now login at some other page and then access elog.
However, I would also need some means of logging out some where else.

For this I propose a new Configuration option "Logout to page" which redirects to another page if set and "Logout to main" is 0.

See the attached patch (against git HEAD)

Does this make sense to you ?

Christof

PS: Many thanks for the autosave mode, I already used it ;-)

Attachment 1: logout_to_page.patch

diff --git a/src/elogd.c b/src/elogd.c
index 601639c..0f976be 100755
--- a/src/elogd.c
+++ b/src/elogd.c
@@ -27975,6 +27975,11 @@ void interprete(char *lbook, char *path)
       if (getcfg(lbs->name, "Logout to main", str, sizeof(str)) && atoi(str) == 1) {
          sprintf(str, "../");
          setparam("redir", str);
+      } else {
+         getcfg(lbs->name, "Logout to page", str, sizeof(str));
+         if (str[0]) {
+             setparam("redir", str);
+         }
       }
       set_sid_cookie(lbs, "", "");
       sid_remove(getparam("sid"));

67883

Wed May 6 12:31:04 2015

Documentation of the webserver authentication

Hi Stefan,

here is a draft of how you could describe the webserver authentication in your docs.

T/Christof

Attachment 1: webserver_auth_doc.patch

diff --git a/doc/adminguide.html b/doc/adminguide.html
index da25388..0568ae3 100755
--- a/doc/adminguide.html
+++ b/doc/adminguide.html
@@ -243,6 +243,37 @@ URL = http://your.proxy.host/subdir/
 
 into elogd.cfg.<p>
 
+<h3><hr><i>Using apache authentication:</i></h3>
+It is also possible to login via an apache-auth module.

+In elogd.cfg you should use the keyword "Webserver" for Authentication:
+  
+<ul><pre>
+Authentication = Webserver
+</pre></ul>
+This triggers elogd to use the environment variable "X-Forwarded-User" as the logged in user.

+A simple example of a apache configuration (including the proxy) is :
+<ul><pre>
+# this required to pass on the generated env-variable X-Forwarded-User to the proxy 
+ProxyPassInterpolateEnv On
+
+ProxyPass /elog/ http://your.host.domain:8080/
+
+&lt;Location  "/elog"&gt;
+        Order allow,deny
+        Allow from all     
+        AuthType Basic
+        AuthName "elog-server"
+        AuthUserFile "/opt/elog/htpasswd"
+        require valid-user
+        RequestHeader unset  Authorization
+        RequestHeader add X-Forwarded-User %{REMOTE_USER}s
+        # elog doesn't like the '@', so we need to cut it
+        RequestHeader edit X-Forwarded-User "@(.*)$" ""
+&lt;/Location&gt;
+</pre></ul>
+
+
+
 <hr><a name="imagemagick"> <div class=section>&nbsp; Installing ImageMagick &nbsp;</div> <p> 
 When images are attached to ELOG entries, thumbnails can be created for quick preview.
 This works also for PDF and PostScript files. ELOG forwards any image operation
diff --git a/doc/config.html b/doc/config.html
index 9848f58..9e98855 100755
--- a/doc/config.html
+++ b/doc/config.html
@@ -2207,6 +2207,22 @@ Options Location = Main Building{a}, New Building{b}, Old Building{c}
     you have to change your password by other means (such as via the Windows
     login if you use a Windows Domain).
     </p>
+    <p>
+    Beside the Kerberos authentication, elogd version 3.0 and higher can be configured to accept a authentication done
+    by the webserver. 
+    <ul>
+      <li>
+        <b><code>Authentication = Webserver</code></b>
+      </li>
+    </ul>
+    </p>
+    <p>
+    You can also combine it with other authentication methods as shown for Kerberos.
+    </p>
+    <p>
+    Elogd is then accepting the username set in the Request-Header "X-Forwarded-User" as already logged in.<br/>
+    To make this work, you need to configure the webserver correctly, as describe in the adminguide.
+    </p>
     
     <p>
       <a name="email" id="email"></a>

67884

Wed May 6 15:13:11 2015

parse a correctly the username in save_user_config when using Webserver authentication

Hi Stefan,

When we use Webserver authentication, we have the correct username already in the variable http_user.

The old way of copying this http_user to "user" is wrong since we don't use the size of http_user.

Instead, just encode the http_user variable directly.

See attached patch against git HEAD.

Christof

Attachment 1: parse_http_user_correctly.patch

diff --git a/src/elogd.c b/src/elogd.c
index 601639c..de4734b 100755
--- a/src/elogd.c
+++ b/src/elogd.c
@@ -13142,12 +13142,13 @@ int save_user_config(LOGBOOK * lbs, char *user, BOOL new_user)
 
    /* if we outsourced the authentication, use external username */
    getcfg(lbs->name, "Authentication", str, sizeof(str));
-   if ( stristr(str, "Webserver")) {
-      strlcpy(user, http_user, sizeof(user));
-   }
 
    /* do not allow HTML in user name */
-   strencode2(user_enc, user, sizeof(user_enc));
+   if ( stristr(str, "Webserver")) {
+      strencode2(user_enc, http_user, sizeof(user_enc));
+   } else {
+      strencode2(user_enc, user, sizeof(user_enc));
+   }
 
    /* check for user name */
    if (!isparam("new_user_name") || *getparam("new_user_name") == 0) {

67922

Wed May 20 18:46:27 2015

Andreas Luedeke

andreas.luedeke@psi.ch

Comment

All

3.1.0

Re: elogd moves elog entries

> Stefan told me that the change was because some users were having thousands of yymmdda.log files
> in the logbook directories, and that sorting them into subdirectories by year at least did something to bring some 
> order.  Possibly to get around the lazy archivers, I suspect.

I'm actually the culprit, who did ask for it.

If you want to know the full story, here it is:
We have our logbook data of our accelerator operation logbooks on AFS (Andrew File System). 
And apparently AFS has a bloody stupid, hard coded limit: 
the total length of all file names in one directory cannot exceed 64k.
Our operation logbooks go back for more than a decade and do contain many, many, many attachment files.
One day - very unexpectedly - we did hit that limit. 
Removing temporary files (generated picture thumbnails) bought us time, and Stefan was nice enough to upgrade ELOG swiftly for us: a big "Thank You" to Stefan!

67923

Wed May 20 19:05:43 2015

David Pilgram

David.Pilgram@epost.org.uk

Comment

All

3.1.0

Re: elogd moves elog entries

> > Stefan told me that the change was because some users were having thousands of yymmdda.log files
> > in the logbook directories, and that sorting them into subdirectories by year at least did something to
bring some 
> > order.  Possibly to get around the lazy archivers, I suspect.
> 
> I'm actually the culprit, who did ask for it.
> 
> If you want to know the full story, here it is:
> We have our logbook data of our accelerator operation logbooks on AFS (Andrew File System). 
> And apparently AFS has a bloody stupid, hard coded limit: 
> the total length of all file names in one directory cannot exceed 64k.
> Our operation logbooks go back for more than a decade and do contain many, many, many attachment files.
> One day - very unexpectedly - we did hit that limit. 
> Removing temporary files (generated picture thumbnails) bought us time, and Stefan was nice enough to upgrade
ELOG swiftly for us: a big "Thank You" to Stefan!


Hi Andreas,

I had no intention of causing any offence with my lazy archiving comment - hope I didn't, sorry if I did.  Just
that sometimes I've hit some limit or other, and
entirely due to my lazy archiving - I only get around to do it when I have to, usually when I've hit a limit, or
some other problem (broken links and orphaned
threads being common ones).   

Personally, I would have found it useful to put the attachments into a separate directory - or at least to allow
the possibility.  Elog as it stands sometimes
can, and sometimes cannot cope with that functionality - and even to try means messing around directly with the
yymmdda.log files.  For me it would have saved me
having duplicates of the same large attachment in two or three different logbooks, if I could always reference
the same Master copy of the attachment.  This was
at the time I was severely memory constrained, and in part forced me to change how I had operated elog, so for
me that need isn't as great as it once was.

David.

67927

Thu May 21 10:59:07 2015

Andreas Luedeke

andreas.luedeke@psi.ch

Comment

All

3.1.0

Re: elogd moves elog entries

I had no intention of causing any offence with my lazy archiving comment - hope I didn't, sorry if I did.

No offence taken :-)

Personally, I would have found it useful to put the attachments into a separate directory - or at least to allow

the possibility. Elog as it stands sometimes can, and sometimes cannot cope with that functionality - and even to try means messing around directly with the

yymmdda.log files. For me it would have saved me having duplicates of the same large attachment in two or three different logbooks, if I could always reference

the same Master copy of the attachment. This was at the time I was severely memory constrained, and in part forced me to change how I had operated elog, so for

me that need isn't as great as it once was.

David.

You can put a reference to the attachment of the other entry in your logbook: elog:67896/1

Or, if it is an image, you can just include it in your new entry like I did below.

Of course this only works if the other logbook is accessible on-line.

But how would you manage access rights to a common attachment folder?

Probably I just did not understand your idea.

Cheers

Andreas

Goto page Previous 1, 2, 3 ... 713, 714, 715 ... 806, 807, 808 Next

ELOG V3.1.5-3fb85fa6