Re: Problem in logging with LDAP and passwd, posted by scott on Tue Mar 19 16:58:52 2024
|
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 |
Re: Problem Naming Logbooks, posted by Stefan Ritt on Wed May 6 15:35:44 2009 
|
| mike cianci wrote: |
|
I have a logbook named "Centaur" (instrument name) for a problem log on an instrument and a logbook named "CentaurNewLot" for
a logbook (Database Like - ELOG format) where we would log reagent lot number changes for that instrument.
The problem is that when I name the logbooks, like I have, it screws up the formatting (List page) of the second log book.
If I rename the second logbook something totally unrelated to the first logbook my originally intended formatting returns.
|
I tried to reproduce your problem but without success. In my case the "CentaurNewLot" looks fine:
so what is different in your case? Can you try with the simple example logbook from the distribution and the add one option after the other to see which one causes the trouble? |
|
Re: Private logbook - no guest access?, posted by Stefan Ritt on Tue Mar 20 13:48:50 2007
|
| Ben Shepherd wrote: | | I want to set up a logbook which you have to be logged in to be able to read entries. I've already got three logbooks which can be viewed by anyone but only logged-in users can modify them. For the fourth one, I want to have a private logbook which can't be read by 'guest' users. Is this possible? |
Per default, logbooks can only be read by logged in users if you use "password file = xxx". It is however possible to make these logbooks readable by 'guest' users if you use "Guest menu commands = xxx" and "Guest list menu commands = xxx". So just remove these two options from your fourth logbook and you get what you want. |
|
Re: Private logbook - no guest access?, posted by Ben Shepherd on Tue Mar 20 14:42:05 2007
|
| Stefan Ritt wrote: |
| Ben Shepherd wrote: | | I want to set up a logbook which you have to be logged in to be able to read entries. I've already got three logbooks which can be viewed by anyone but only logged-in users can modify them. For the fourth one, I want to have a private logbook which can't be read by 'guest' users. Is this possible? |
Per default, logbooks can only be read by logged in users if you use "password file = xxx". It is however possible to make these logbooks readable by 'guest' users if you use "Guest menu commands = xxx" and "Guest list menu commands = xxx". So just remove these two options from your fourth logbook and you get what you want. |
Thanks! I actually saw that in the config documentation, but I had assumed that it didn't work. Turns out I'd left those two options in my [global] section as well. Oops! |
|
Re: Print Function, posted by Stefan Ritt on Wed Dec 5 21:33:48 2007
|
| Adam Blandford wrote: |
|
While it is possible to print a logbook using the standard web browser print command in the Full or Summary view, a dedicated print function allowing the user to print out a hardcopy of a particular logbook would be very helpful.
Cheers
Adam
P.S. Thankyou for the response in elog:65671
|
This is possible since the beginning: Click on Find, then check Display full entries and Printable output and hit Search. You get then a single page containing all entries from the logbook which you can easily print to get a hardcopy. |
|
Re: Preset text overriden after preview, posted by Stefan Ritt on Wed Oct 26 16:17:18 2005
|
| Yoshio Imai wrote: | | This form appears correctly, but after filling in the form, clicking on "Preview" leads to an error: the preview text is correct, but the actual text entry field is overriden again with the empty form. |
Thanks for reporting this bug. It's fixed in revision 1534.
- Stefan |
Re: Preset text overriden after preview, posted by Yoshio Imai on Fri Oct 28 10:42:44 2005
|
| Stefan Ritt wrote: |
Thanks for reporting this bug. It's fixed in revision 1534.
- Stefan |
I just tested it, it works. Thanks! |
|
Re: Preset text Dont work more!, posted by Stefan Ritt on Tue Mar 29 11:30:25 2005
|
> I'am using Elog V2.5.8-1 and the "Preset Text" option don't work more since
> I've updated Elog. could you fix it?
I tried with the example elogd.cfg and it worked there, so it must have to do
with your special configuration. Can you send me your elogd.cfg so that I could
reproduce your problem?
- Stefan |