Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 364 of 808  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Hide attachments  Show only new entries    6457 Entries 
Goto page Previous  1, 2, 3 ... 363, 364, 365 ... 806, 807, 808   Next  
ID Date Icon Author Author Email Category OS ELOG Version Subjectdown
  69763   Tue Mar 19 16:58:52 2024 Reply scottshiva.ps@stfc.ac.ukQuestionLinuxELOG V3.1.3-Re: Problem in logging with LDAP and passwd
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
  66348   Wed May 6 15:35:44 2009 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.7.5-2185Re: Problem Naming Logbooks

 

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:

Capture.png

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?

  2172   Tue Mar 20 13:48:50 2007 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.2-1739Re: Private logbook - no guest access?

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.
  2173   Tue Mar 20 14:42:05 2007 Reply Ben Shepherdbjs54@dl.ac.ukQuestionLinux2.6.2-1739Re: Private logbook - no guest access?

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!
  65675   Wed Dec 5 21:33:48 2007 Reply Stefan Rittstefan.ritt@psi.chRequestWindows2.7.0-1964Re: Print Function

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.

  1487   Wed Oct 26 16:17:18 2005 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.6.0beta5Re: Preset text overriden after preview

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
  1488   Fri Oct 28 10:42:44 2005 Smile Yoshio Imaiimai@kph.uni-mainz.deBug reportLinux2.6.0beta5Re: Preset text overriden after preview

Stefan Ritt wrote:

Thanks for reporting this bug. It's fixed in revision 1534.

- Stefan


I just tested it, it works. Thanks!
  1030   Tue Mar 29 11:30:25 2005 Reply Stefan Rittstefan.ritt@psi.chBug reportWindowsV2.5.8-1Re: Preset text Dont work more!
> 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
Goto page Previous  1, 2, 3 ... 363, 364, 365 ... 806, 807, 808   Next  
ELOG V3.1.5-3fb85fa6