Keeping the global and individual logbooks in sync is not possible. So indded my proposal is a cumbersome solution in your case. We do have "restrict edit" which lets users only edit their own entries, but we do not have "restrict view". Maye some thought for a future version of elog.

Stefan

Hi Team,

Current configuration

=================

OS: Ubuntu 22.04.4 LTS

ELOG version: elog/jammy,now 3.1.3-1-1build2 amd64 [installed]

Installation method: apt install elog

Configuration file: /etc/elogd.cfg

LOGBOOKDIR= /var/lib/elog/logbooks}
RESOURCEDIR= /usr/share/elog

I had an ELOG server set up in the Windows server which is authenticated using a Password file. Recently, I have migrated the ELOG server to the Ubuntu server. I installed ELOG from the Ubuntu repository (apt install elog) and copied over the logbook and configuration file from the windows server to the new Ubuntu server. In the server, the configuration file was set to /etc/elog.conf by default. I have modified the init file and set the configuration file to /etc/elogd.cfg (this conf file is copied from the Windows server) which includes all the settings. After moving to the Ubuntu server I would like to authenticate users using the password file and LDAP. Could someone help me how to configure LDAP in my installation style?

The global configuration that is found on my installation is as follows:

###################################

; Global settings

Password file = elog.pwd
Self register = 1
Admin user = a, b,c, d, e, Iafdsel

Suppress Email to users = 1
SMTP host = example.com

Time format = %Y-%m-%dT%H:%M:%S
Date format = %Y-%m-%d

Restrict edit time = 2
Restrict edit = 1

Allow HTML = 1
Max content length = 209715200
Save drafts = 0
###################################

Should I add the below modification (by editing the necessary fields) to the current configuration? Will that make the LDAP and normal password file work?

############################

• Enable LDAP authentication in the Makefile by setting USE_LDAP = 1   (I am not sure if I need to do this in my installation style. If yes, how do i do this?)

• Authentication = LDAP
• LDAP server = ldap://example.org:389
• LDAP userbase = ou=People;dc=example,dc=org
• LDAP login attribute = uid
• LDAP register = 1

​############################
 

Can someone guide me on what changes I need to make for this?

Many Thanks,
Scott

Hello, the "drop attachments here..." feature is very useful, especially when I have multiple files. I can drag them all over in one operation, however I have noticed that this feature only works well in the IE browser.

It does not work reliably in Safari/Chrome/Firefox. I have tired in both 3.1.3 and 3.1.2. I also have the same symptom on the Demo log book of this site.

Please advise. Thank you for the continued development of Elog.

-Michael Hibbard

Hi, I was wondering if this is possible. I've tried to sort on anything other than the first few fields and although the screen refreshes like it is 'doing something', it does NOT sort. Sometimes it will take me to the last page of my data, but still no sorting. I use Debian Linux verson of Elog. There have been no other issues. I need to figure out how to do this without parsing it to another program first. Thanks again for this wonderful program :)

John

Sorting does work fine, if you do it correctly. From your post I cannot even guess what you've tried - let alone tell you what you did wrong.

Please post your config, some example entries and a description of what you've tried, what you expected to happen and what actually happened. Screenshots are often very useful as well.

Hi Andrea and thank you soo much  for your kind and prompt reply! I believe the issue will be solved as I have the information I need to proceed. I was just wanting to verify that sorting indeed is alloud on ALL fields.  I cannot send the exact config as it is a work project, but I can replicate with fake fields and data if necessary in the future. I believe my errors are because I am either using field names which are 'special' to the system, or some other limitation. I will try compiling and see if that helps. 

John

I'm trying to wrap our elog instance to our company domain which is lbl.gov

I add this entry below (without quotes) to elogd.cfg and it's not working.  the world can see our logbooks

" Hosts Allow = *.lbl.gov ".

can someone help?

Hi Susan,

• Hosts allow = <list>
• Hosts deny = <list>

These two settings can be used to restrict the access to the logbook to certain computers. It is similar to the UNIX hosts.allow and hosts.deny files. The list can consist of individual host names or IP numbers, subnet masks like 123.213. (note the trailing '.') or .mit.edu, or the word All. The following rules are applied:

• Access will be granted when a host matches a pattern in "hosts allow".
• Otherwise, access will be denied when a host matches a pattern in "hosts deny".
• Otherwise, access will be granted.

These rules are applied before any password is checked. To debug problems, start elogd with the "-v" flag, in which case the rule checking is printed on the screen.