Hello,

After enabling SSL=1 in /usr/loca/elog/elogd.cfg file, HTML editor loading very long. 

After changing SSL to 0, everything work flawlessly.

Does anyone know what can cause this behaviour?

Best Regards
Daniel

Hello,

I created new certificate, but it doesn't help with resolving this problem.

Does someone have and idea how to resolve it?

Best Regards

Daniel

Hello,

I found that someone else had the same issue - https://dev.ckeditor.com/ticket/10874#no1

In Firefox I do not have problems, but in Chrome and Edge i have. 

His solution was:

My problem is solved. The .htaccess file sents any request to the login page. Therefore CKEditor could not reach the CSS file. Thanks for helping!

Sinse I don't use apache webserver, I don't know what should I do. 

It looks that also in my case problem is with file progressjs.min.css (please look at attached screenshot)

Anyone have solution for this?

Best Regards

Daniel

Hello,

I found that someon

Hello,

I found that someone else had the same issue - https://dev.ckeditor.com/ticket/10874#no1

But I don't know why

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

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.