Andreas Wandel wrote:
> 
> Hi,
> I've tried to build midgard from scratch in the past on debian 2.2 ->
> failed (maybe because I am not so familiar with this distribution, but I
> tried it because of it's stability :-( )
> So, with knowing thet SuSE includes Midgard to their distribution,
> I swiched back and went into trouble with their configuration:

Which version Midgard would that be?

> They changed the Host table like this (ports and prefix)

looks good.


> and added to httpd.conf

Looks good.

> -------------------------------------------------------------------------
> 
> Midgard was accessable on both ports, but there were
> 
> 1. no auth request

Then I must assume that you're using 1.2.5. Add to your httpd.conf:

<Files midgard-root.php3>
require valid-user
AuthName Midgard
AuthType Basic
</Files>

> 2. no way to change any information in the data base

This is caused by not having auth enforced, see #1

> 3. no 'midgard' directory (example and images were under htdocs)

If that's the SuSE install then their installer got it wrong. Moving
them should fix it.

> After inserting 'DocumentRoot /usr/local/httpd/midgard' to the virtual
> hosts and moving example and images to this dir, the authentication dialog
> apeared in the browser, but the apache log file said after trying
> admin/password :

Then my guess is that the httpd.conf has a piece like

<Directory /usr/local/httpd/midgard>
require valid-user
AuthName Midgard
AuthType Basic
</Files>

with the rootfile being in that directory. Do not use this directory as
your
document root. The rootfile doesn't need to be in your documentroot and
I advice
against it.

What's happening is that you're requesting the images from that
directory after
you changed the documentroot, and since the directory is configured to
enforce auth,
apache pops up the login dialog. Only to find out moments later that
there's noone
servicing the authentication phase.

> No such file or directory: Could not open password file: /etc/httpd/passwd

Apache falls back to it's own password file if no other module has doen
the authentication
phase. But since you haven't supplied an apache password file for the
directory, it can't.

> What's wrong? Should I remove some other mod_auth* ?

No. Include the <Files...> section or make sure that the rootfile is in
a directory that
enforces auth. Set the document root to something else, create a
directory 'midgard'
there and move the images directories into it.

1.4 changes some of this as it no longer relies on apache to enforce
auth.

Emile

--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org

To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]

Reply via email to