Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon1.gif   restrict access, posted by Gerald Ebberink on Wed Jun 21 22:11:15 2006 
    icon2.gif   Re: restrict access, posted by Stefan Ritt on Thu Jun 22 08:04:13 2006 
       icon2.gif   Re: restrict access, posted by Gerald Ebberink on Thu Jun 22 11:29:17 2006 
          icon2.gif   Re: restrict access, posted by Stefan Ritt on Thu Jun 22 11:38:38 2006 
             icon2.gif   Re: restrict access, posted by Gerald Ebberink on Thu Jun 22 12:10:00 2006 
                icon2.gif   Re: restrict access, posted by Stefan Ritt on Fri Jun 23 12:29:30 2006 elogd.cfgCapture.jpgCapture.jpg
                   icon2.gif   Re: restrict access, posted by Gerald Ebberink on Fri Jun 23 13:16:57 2006 
                      icon2.gif   Re: restrict access, posted by Stefan Ritt on Fri Jun 23 13:43:03 2006 
                         icon2.gif   Re: restrict access, posted by Gerald Ebberink on Fri Jun 23 14:57:02 2006 elog.conf
                         icon2.gif   Re: restrict access, posted by Gerald Ebberink on Mon Jul 17 13:20:07 2006 
Message ID: 1860     Entry time: Fri Jun 23 12:29:30 2006     In reply to: 1854     Reply to this: 1861
Icon: Reply  Author: Stefan Ritt  Author Email: stefan.ritt@psi.ch 
Category: Question  OS: Linux  ELOG Version: 2.6.1 
Subject: Re: restrict access 
Even with your config file (I just changed the URL) I get the correct behaviour:



and after I supply my credentials:



My full elogd.cfg is attached for your reference.

I'm pretty sure that you did not delete your old cookies. Try from another computer. Make sure to have the most recent version of elog. Start the elogd daemon with the "-v" flag and watch the communication. I get for example:
GET / HTTP/1.1
Host: localhost:8080
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.4) Gecko/20
060508 Firefox/1.5.0.4
Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plai
n;q=0.8,image/png,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Cookie: urem=1


==== Return ================================
....

As you can see, only the "urem" cookie is present. After I logged in, I get:
Cookie: urem=1; unm=stefan; upwd=Z2suZgFszgg==

These cookies identify you as logged in, so the login screen does not appear any more.
Attachment 1: elogd.cfg  1 kB  | Hide | Hide all
[global]
logbook tabs = 1
port = 8080
URL = http://localhost:8080/

Protect selection page = 1
Password file = passwd
Self register = 0
Admin user = stefan

Group World = Procedures, Work
Group Work = Company, Company2
Group Company = twiddle
Group twiddle = Panels, Bond

[Procedures]
Theme = default
Comment = General Procedures for use with
Attributes = Author, Category, Subject
Options Category = Maintenance, Alignment
Required Attributes = Author, Category

[Company2]
Theme = default
Comment = Company2 project Page
Attributes = Author, Category, Subject
Options Category = Scheduling, During Progress, During measuring, After
Required Attributes = Author

[Panels]
Theme = default
Attributes = Author, Category, Subject
Options Category = Scheduling, During Progress, During measuring, After
Required Attributes = Author
Expand default = 2
Protect selection page = 1

[bond]
Theme = default
Attributes = Author, Category, Subject
Options Category = Scheduling, During Progress, During measuring, After
Required Attributes = Author

ELOG V3.1.5-3fb85fa6