Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon5.gif   PAM authentication question, posted by David Wallis on Tue Nov 5 21:42:50 2019 
    icon2.gif   Re: PAM authentication question, posted by Jan Christoph Terasa on Sun Nov 17 14:55:11 2019 
       icon2.gif   Re: PAM authentication question, posted by David Wallis on Thu Nov 21 18:10:28 2019 
          icon2.gif   Re: PAM authentication question, posted by Jan Christoph Terasa on Thu Dec 19 17:46:33 2019 
          icon2.gif   Re: PAM authentication question, posted by Laurent Jean-Rigaud on Fri Jan 24 17:33:14 2020 
             icon2.gif   Re: PAM authentication question, posted by Jan Christoph Terasa on Fri Jan 24 18:13:03 2020 
                icon2.gif   Re: PAM authentication question, posted by Laurent Jean-Rigaud on Fri Jan 24 18:22:52 2020 
                   icon2.gif   Re: PAM authentication question, posted by Laurent Jean-Rigaud on Fri Jan 31 15:39:17 2020 
Message ID: 69093     Entry time: Fri Jan 24 18:22:52 2020     In reply to: 69092     Reply to this: 69102
Icon: Reply  Author: Laurent Jean-Rigaud  Author Email: lollspam@free.fr 
Category: Question  OS: Linux  ELOG Version: V3.1.4-283534d 
Subject: Re: PAM authentication question 

Hi,

Before le pam module link, yes.

After adding it, I wait some seconds before new login window popups with password error message.

 

Jan Christoph Terasa wrote:

Hi Laurent,

does the ELOG server show the window immediately before even showing the login mask?

 

Christoph

Laurent Jean-Rigaud wrote:

Hi,

First, thanks to ELOG tool !

 

I'm trying to swicth a ELOG 3.1.2 server with local passwd DB to GIT version builded with SSL/PAM/LDAP options. I reuse the buildrpm script which generates correctly RPM files.

After installing on EL6 x86_64 server, i update the elogd.conf file according to GIT version doc :

  • Authentication = PAM
  • Password file = /usr/local/elog/elog_users.pam   (new file as i want to keep the old local DB)
  • Self register = 3

I add a link for pam module :

$ ll /etc/pam.d/elogd
lrwxrwxrwx 1 root root 11 Jan 24 16:23 /etc/pam.d/elogd -> system-auth

elogd starts well

elogd 3.1.4 built Jan 24 2020, 07:34:02 revision 283534d
Config file  : /usr/local/elog/elogd.cfg
Resource dir : /usr/local/elog/
Logbook dir  : /usr/local/elog/logbooks/
Falling back to default group "elog"
Falling back to default user "elog"
CKeditor detected
Falling back to default group "elog"
Falling back to default user "elog"
Going to execute: /bin/sh -c "convert -version" > /tmp/elog_okY7qv 2>&1
Falling back to default group "elog"
Falling back to default user "elog"
Going to execute: /bin/sh -c "/usr/bin/convert -version" > /tmp/elog_xBge3f 2>&1
Falling back to default group "elog"
Falling back to default user "elog"
Going to execute: /bin/sh -c "/usr/local/bin/convert -version" > /tmp/elog_GfKWF0 2>&1
Falling back to default group "elog"
Falling back to default user "elog"
Going to execute: /bin/sh -c "/opt/local/bin/convert -version" > /tmp/elog_uZtajL 2>&1
ImageMagick NOT detected. Image scaling will not work.
Indexing logbook "logbook1" in "/usr/local/elog/logbooks/logbook1/" ... ok
Indexing logbook "logbook2" in "/usr/local/elog/logbooks/logbook2/" ... ok
Server listening on port 8080 ...

When i try to connect, ELOG login window shows "Invalid user name or password!" .

The logfile (level 9) shows :

24-Jan-2020 16:36:28 [IP] POST /logbook1/ HTTP/1.1
24-Jan-2020 16:36:28 [IP] {MCO} LOGIN user "toto" (attempt)
24-Jan-2020 16:36:28 [IP] {MCO} [PAM] Starting authentication for user toto
24-Jan-2020 16:36:29 [IP] {MCO} [PAM] Authentication not successful for user toto

The problem appears for all Linux users as well.

Does i miss something ?

Thanks for help.

Laurent

 

 

David Wallis wrote:

Hi Christoph,

Thanks for looking into this, if you can enable PAM + File, our users would be very happy!

The pam.d issue is probably related to CentOS/Red Hat, since our PAM expert warned me that it might be necessary.

Jan Christoph Terasa wrote:
David Wallis wrote:

I'm testing the PAM authentication feature, and have a couple questions, a suggestion, and a comment.

First the comment... it was pretty easy to get working, and is exactly what we need here, so thanks! Our PAM stack here is designed to allow logins with Active Directory, LDAP, or local accounts, so the PAM option preserves all of that.

The suggestion: In order to make it work, I had to add a symbolic link in /etc/pam.d:
    elogd -> system-auth
That might be considered for addition to the documentation (this was on Red Hat Enterprise Linux 7.7)

The questions:

  1. The docs indicate that "Self register" must be set to >= 1, but in the code (elogd.c, line 26453), if the PAM module is enabled, Self register is overriden to 0. The result is that no "register as new user" link is displayed on the login screen. Is that the intent?
  2. Related... can PAM and File authentication both be enabled? We have some logbooks that are used by both internal people (with an A/D account) and outside collaborators that get local elog accounts. This works with LDAP + File, can it work with PAM?

Thanks in advance!

 

David, thank you for reporting on your findings regarding the PAM feature. I will look into the points you mentioned:

0. On my machines (Debian testing and stable) I did not have to add anything to /etc/pam.d, but apparently Debian just uses implicit defaults then, and REHL might insist on using excplicit settings. Adding a hint in the documentation is certainly useful, thank your for the suggestion. Maybe elog should provide a pam.d config file (which can be installed/adapted by package maintainers for various OSes).

1.+2. If I remember correctly, I intentionally disabled registration when using the PAM backend, because users will register using their passwd/LDAP/NIS users, and new users can only be regustered using the appropriate tools for the authentication mechanism used. This might not be correctly reflected in the docs, I will check that. In the light of question 2., I can also re-investigate that policy, so that logins will check against both the elog user database and PAM. Self-registering can then be enabled again, and new registrees will go to the elog database. I will try to bringthe code in line with how LDAP works.

 

regards,

Christoph

 

 

 

 

ELOG V3.1.5-fe60aaf