For Windows it's more than just getting the .exe. Users want an installer. I used the Nullsoft Scriptable Installer (NSI), but I have no clue if this still works today. But there is still the elog.nsi script in the repository. Next, users want elogd as a service running in the background as a "service". I'm pretty sure the old way of doing that has changed and one would at least have to test this. Unfortunatley I switched to MacOSX about ten years ago (actually most of ELOG has been developed under Windows, but these days are gone), so I'm kind of illiterate in the Windows world now and don't have any time to change that.

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

Elogd for windows has an option -install which normally does it. Is it working on last Windows version (or the one enclosed in elog:Forum/69664) ?

If Yes, a simple install-as-a-service.bat can be added to archive :-)

.

Laurent

Hi Stefan,

Some updates for Windows version.

I spent last WE to try to build ELOG on Windows from MSVCODE, MSCV, crosschain tool under linux etc, but in vain.

ELOG MSVC projects file are obsolete for last MS C++, and after migration, so much error or missing libs for SSL/Ldap/krb5 which should be built... I drop the sponge :-P

With mingw64 under Linux (docker/Debian), the code has also to be updated (C++11), but I don't get a build after all (also libs missing and must be built).

Finally, I can build Windows version from Windows with CygWin gcc-c++ as I did in the past. All the dependencies are available from CygWin installer. I got problems with strlcpy file missing, need to drop inlcude from elog.c and elogd.h as mxml doesn't include it anymore...

I find a Win64 CI/CD solution on AppVeyor which is free for OSS project. After creating account and add link to my ELOG test Bitbucket repo, ad new files (appveyor.yml, buildming script, update NSIS script for CygWin DDL, add tool for service), it builds automatically an elog-ver-release.exe artifact : (current build from GIT with SSL/LDAP/KRB5 available on month up to March 3, 2024 : https://ci.appveyor.com/api/buildjobs/logp7r8f0kcjq9pp/artifacts/elog-3.1.5-a720145.exe)

I installed this NSIS bundle on my PC and it's starting fine as a service.

The link info from EXE :

$ ldd /cygdrive/c/Program\ Files\ \(x86\)/ELOG/elogd.exe
        ntdll.dll => /cygdrive/c/Windows/SYSTEM32/ntdll.dll (0x7ffdb1fb0000)
        KERNEL32.DLL => /cygdrive/c/Windows/System32/KERNEL32.DLL (0x7ffdb0dc0000)
        KERNELBASE.dll => /cygdrive/c/Windows/System32/KERNELBASE.dll (0x7ffdaf950000)
        cygwin1.dll => /cygdrive/c/Program Files (x86)/ELOG/cygwin1.dll (0x7ffcedc30000)
        cygkrb5-3.dll => /cygdrive/c/Program Files (x86)/ELOG/cygkrb5-3.dll (0x3fe0a0000)
        cyglber-2.dll => /cygdrive/c/Program Files (x86)/ELOG/cyglber-2.dll (0x3fe040000)
        cygldap-2.dll => /cygdrive/c/Program Files (x86)/ELOG/cygldap-2.dll (0x3fdf20000)
        cygssl-3.dll => /cygdrive/c/Program Files (x86)/ELOG/cygssl-3.dll (0x3fd0d0000)
        cyggcc_s-seh-1.dll => /cygdrive/c/Program Files (x86)/ELOG/cyggcc_s-seh-1.dll (0x3ff1d0000)
        cygstdc++-6.dll => /cygdrive/c/Program Files (x86)/ELOG/cygstdc++-6.dll (0x3fcee0000)
        cygk5crypto-3.dll => /cygdrive/c/Program Files (x86)/ELOG/cygk5crypto-3.dll (0x3fe170000)
        cygkrb5support-0.dll => /cygdrive/c/Program Files (x86)/ELOG/cygkrb5support-0.dll (0x3fe080000)
        cygcom_err-2.dll => /cygdrive/c/Program Files (x86)/ELOG/cygcom_err-2.dll (0x3ffe90000)
        cygintl-8.dll => /cygdrive/c/Program Files (x86)/ELOG/cygintl-8.dll (0x3fe450000)
        cygcrypto-1.1.dll => /cygdrive/c/Program Files (x86)/ELOG/cygcrypto-1.1.dll (0x3ffbc0000)
        cygsasl2-3.dll => /cygdrive/c/Program Files (x86)/ELOG/cygsasl2-3.dll (0x3fd3e0000)
        cygssl-1.1.dll => /cygdrive/c/Program Files (x86)/ELOG/cygssl-1.1.dll (0x3fd170000)
        cygcrypto-3.dll => /cygdrive/c/Program Files (x86)/ELOG/cygcrypto-3.dll (0x3ff800000)
        cygiconv-2.dll => /cygdrive/c/Program Files (x86)/ELOG/cygiconv-2.dll (0x3fe540000)
        cygz.dll => /cygdrive/c/Program Files (x86)/ELOG/cygz.dll (0x3fc790000)

I will send you the files/patchs if AppVeyor could be used for Windows CI/CD in your project.

Bye,

Laurent

NB: the AppVeyor build log enclosed, need some cleanup...

Hi Everybody,

I import a logbook from csv file, with a number for laboratory's notebook, which can be use by multiple intern. I'd like to add a "reply to" when the number is the same, it's like a "move to" but in the same logbook.

Thanks in advance for your help

Hi Members,

I have compiled and installed ELOG in Ubuntu 22.04. My ELOG version is 3.1.5 revision fc6679b. I would like to use both the password file (../logbooks/elog.pwd) and the LDAP for authentication purpose. In addition to this, new users should be able to register and existing users should be able to reset their password.

Anyone could shed some light on how to do this in the configuration file?

Thanks,
Scott

Hi Stefano,

I also tried to set up LDAP authentication and password file-based authentication using the same settings as yours, which is not working as expected. It does work only with the LDAP authentication and not with the password file now. If I remove the LDAP-based parameters from the configuration file it works then password files start working.

I think multiple ways of authentication do not work concurrently.


Is that issue still existing for you or is it resolved?

Thanks,
Scott


----

> Dear experts,
>    I have a logbook which has authentication as follow
> 
> Authentication = LDAP, File
> Password file = PASSWD.file
> LDAP server = ldaps://it-ldap-XXX.XXX.XX:1636
> LDAP userbase = ou=people,ou=RGY,o=XXX,c=XX
> LDAP login attribute = uid
> LDAP register = 0
> Self register = 0
> Allow password change = 0
> 
> Some of the my user (but not all) have issue in accessing this protected elogbook.
> The ldap password is correct (we checked).
> What I see in the log is as follow:
> 
> 22-Feb-2021 11:25:51 [XXX.YYY.ZZZ.QQ] {Beam Run} LOGIN user "USERNAME" (attempt)
> 22-Feb-2021 11:25:59 [XXX.YYY.ZZZ.QQ] {Beam Run} LOGIN user "USERNAME" (attempt)
> 
> The user USERNAME is present in PASSWD.file.
> 
> For other user, for which the login works, I do see an (attempt) and then (success)
> 
> we tried the standard stuff: clear cache/cookies and with different browser. We also tried to remove the user from PASSWD.file and 
> create it again, but nothing has worked.
> 
> Any suggestion how I can debug this problem?
> 
> Thanks in advance,
>   Stefano

Hello all,

I am installing elog on an Rocky Linux instance. Have dependensy problem. 

rpm -Uvh elog-latest.el7.x86_64.rpm 

error: Failed dependencies:

    liblber-2.4.so.2()(64bit) is needed by elog-3.1.5-1.el7.x86_64

    libldap-2.4.so.2()(64bit) is needed by elog-3.1.5-1.el7.x86_64

    libssl.so.10()(64bit) is needed by elog-3.1.5-1.el7.x86_64

    libssl.so.10(libssl.so.10)(64bit) is needed by elog-3.1.5-1.el7.x86_64

Any clues from developers to resolve it and keep the software working. Thank you in advance!

Bests, Nina