Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 223 of 796  Not logged in ELOG logo
ID Dateup Icon Author Author Email Category OS ELOG Version Subject
  1848   Wed Jun 21 17:03:23 2006 Reply Stefan Rittstefan.ritt@psi.chBug reportWindows2.6.1-6Re: Corrupt page link

Ulrich Trüssel wrote:
If a loggbook contains more than one page of entries, above and under the list are links for changing the page by number (or privous / last and all) conatining links looking like "http://localhost:8080/logbook/page2?mode=mode". This is the correct link and will work until Version 2.6.1-5!

In Version 2.6.1-6 the link is corrupted and look always like "http://localhost:8080/logbook/pag"


Well, in this forum the link is fine, so it must have to do with your special configuration. Can you try with the demo logbook and find out which configuration option causes this problem?
  1849   Wed Jun 21 18:36:06 2006 Question Jeremy Perkinsperkins@egret.sao.arizona.eduQuestionLinux Hosts Allow and Password File
I'm trying to set up an elog that uses a password file using the "Password file = /blah" directive as well as the "Hosts allow = myhost.mydomain" directive. I used the -v command and watched the messages and elogd is recognizing that I am connecting from an allowed host but the login page is still appearing. Is there a way to use both of these?
  1850   Wed Jun 21 22:11:15 2006 Entry Gerald Ebberinkg.h.p.ebberink@nclr.nlQuestionLinux2.6.1restrict access
Dear all,

I am trying to get elog used in our company but I need some help.
I have two small questions:

-1- how can I restrict the access 
of a certain user such that he can only see certain logbooks. 
But also not showing the other logbooks on the selection page.
So we could have a tree like this:

Stage one
|
|->Stage 2
       |
       |
      / \
     |   |
    Co1 Co2
    /     \
  job     job

So when Co1 logs in the should not be able to see Co2 and the attached job

-2- How can I have a login page instead of the logbook selection page.
When I insert the password statement the config, I get a blank page.
  1851   Thu Jun 22 08:04:13 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.1Re: restrict access
> -1- how can I restrict the access 
> of a certain user such that he can only see certain logbooks. 

This can be achieved with the "Login user = ..." option.

> But also not showing the other logbooks on the selection page.

You could try to use "top groups". This gives you "separate" groups of logbooks, so you could make a public tree
seen by everybody and private trees only seen by a few people. Please read the documentation for details.

> -2- How can I have a login page instead of the logbook selection page.
> When I insert the password statement the config, I get a blank page.

You get a login page instead of the selection page if the "Password file = " statement is in the [global] section
and "Protect selection page = 1". You might have to delete all cookies in your browser if you move the password
file statement between the [global] and the logbook sections, because otherwise the old cookies might prevent you
from logging out.
  1852   Thu Jun 22 08:09:11 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux Re: Hosts Allow and Password File

Jeremy Perkins wrote:
I'm trying to set up an elog that uses a password file using the "Password file = /blah" directive as well as the "Hosts allow = myhost.mydomain" directive. I used the -v command and watched the messages and elogd is recognizing that I am connecting from an allowed host but the login page is still appearing. Is there a way to use both of these?


You misunderstand something. The "Password file = ..." statement turns on user level access, that means each user has to log in and identify himself this way in a unique way (so that you know who wore a certain logbook entry etc.). This has nothing to do with the "Hosts allow/deny" statements, which works separately. So if you combine "hosts allow" with "password file", this means that only users from the password file can log in from certain hists, but they still have to identify themselves with their username and password. If you want to log into a logbook without supplying a password from certain hosts, then you remove the "password file" statement. But then anyone from that host can write logbook entries, so you loose the user identification.
  1853   Thu Jun 22 11:29:17 2006 Reply Gerald Ebberinkg.h.p.ebberink@nclr.nlQuestionLinux2.6.1Re: restrict access
> > -1- how can I restrict the access 
> > of a certain user such that he can only see certain logbooks. 
> 
> This can be achieved with the "Login user = ..." option.

That is what I found in the mean time. And it works like a charm.

> 
> > But also not showing the other logbooks on the selection page.
> 
> You could try to use "top groups". This gives you "separate" groups of logbooks, so you could make a public tree
> seen by everybody and private trees only seen by a few people. Please read the documentation for details.

I'm now using this (I had to redesign our tree for that)

> > -2- How can I have a login page instead of the logbook selection page.
> > When I insert the password statement the config, I get a blank page.
> 
> You get a login page instead of the selection page if the "Password file = " statement is in the [global] section
> and "Protect selection page = 1". You might have to delete all cookies in your browser if you move the password
> file statement between the [global] and the logbook sections, because otherwise the old cookies might prevent you
> from logging out.

This is not working for me, in Mozilla Firefox I'm still getting a blank page, where IE is giving me an error
stating
that the page is unavailable
  1854   Thu Jun 22 11:38:38 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.1Re: restrict access
> > You get a login page instead of the selection page if the "Password file = " statement is in the [global]
section
> > and "Protect selection page = 1". You might have to delete all cookies in your browser if you move the password
> > file statement between the [global] and the logbook sections, because otherwise the old cookies might
prevent you
> > from logging out.
> 
> This is not working for me, in Mozilla Firefox I'm still getting a blank page, where IE is giving me an error
> stating that the page is unavailable

If I use following config file:


[global]
port = 8080
password file = passwd
protect selection page = 1

[demo1]
Attributes = Author, Type, Category, Subject

[demo2]
Attributes = Author, Type, Category, Subject


then I don't get a blank page. An unavailable page you should only get whan you use top groups, and want to
access the root. 
  1855   Thu Jun 22 12:10:00 2006 Reply Gerald Ebberinkg.h.p.ebberink@nclr.nlQuestionLinux2.6.1Re: restrict access
> > > You get a login page instead of the selection page if the "Password file = " statement is in the [global]
> section
> > > and "Protect selection page = 1". You might have to delete all cookies in your browser if you move the password
> > > file statement between the [global] and the logbook sections, because otherwise the old cookies might
> prevent you
> > > from logging out.
> > 
> > This is not working for me, in Mozilla Firefox I'm still getting a blank page, where IE is giving me an error
> > stating that the page is unavailable
> 
> If I use following config file:
> 
> 
> [global]
> port = 8080
> password file = passwd
> protect selection page = 1
> 
> [demo1]
> Attributes = Author, Type, Category, Subject
> 
> [demo2]
> Attributes = Author, Type, Category, Subject
> 
> 
> then I don't get a blank page. An unavailable page you should only get whan you use top groups, and want to
> access the root. 
I use the folowing file and do get this error (the company names and other sensitive information has been changed to
something simular but not so sensitive)

[global]
logbook tabs = 1
port = 80
Logbook dir = /srv/elog/logbooks/
URL = http://my.domain/

Protect selection page = 1
Password file = /srv/elog/passwords/main.passwd
Self register = 0
Admin user = Gerald


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
Subdir = Some/dir

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

[Panels]
Theme = default
Attributes = Author, Category, Subject
Options Category = Scheduling, During Progress, During measuring, After
Required Attributes = Author
Subdir = Some/dir
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
Subdir = some/dir
ELOG V3.1.5-2eba886