Re: Problem with access to password protected area

Michael Forster <admin@muckworld.com> wrote:
> After 3 attempts I get the 403 Authorisation Required Page.

Good, it means that he said the .htaccess file, but for some reasons
can't validate the user. Check in the .htpasswd file if the username
is present and something that look like a password is there (it's
encrypted, so you can't read it).

Them check in the apache error_log file if there are information
related to the problem, I think that it could be a problem with
accessing the .htpasswd file. Maybe it doesn't have enough
autorization.

Davide

"Davide Bianchi" <davideyeahsure@onlyforfun.net> wrote in message
news:bhge60$euug$1@ID-18487.news.uni-berlin.de...
> Michael Forster <admin@muckworld.com> wrote:
> > After 3 attempts I get the 403 Authorisation Required Page.
>
> Good, it means that he said the .htaccess file, but for some reasons
> can't validate the user. Check in the .htpasswd file if the username
> is present and something that look like a password is there (it's
> encrypted, so you can't read it).
>
> Them check in the apache error_log file if there are information
> related to the problem, I think that it could be a problem with
> accessing the .htpasswd file. Maybe it doesn't have enough
> autorization.
>
I found the following errors
[Thu Aug 14 23:07:58 2003] [error] [client 10.69.70.202] guest: not a valid
FDN: /forsale
[Thu Aug 14 23:08:00 2003] [error] [client 10.69.70.202] guest: not a valid
FDN: /forsale
[Thu Aug 14 23:08:01 2003] [error] [client 10.69.70.202] guest: not a valid
FDN: /forsale
[Thu Aug 14 23:08:03 2003] [error] [client 10.69.70.202] guest: not a valid
FDN: /forsale

Mike.

"Michael Forster" <admin@muckworld.com> wrote in message
news:3f3c0373$1@news.userve.net...
>
I found the following information..So I will try removing the AuthLDAP
module and see if it works.

Mike

Symptom
You are trying to use the authentification method of Apache by using the
file .htaccess. But that fails. In the log file /var/log/httpd/error_log you
find the following:
[Wed Jul 25 12:45:11 2001] [error] [client x.x.x.x] wm: not a valid FDN:
/dir/
Cause
The package authldap, which is responsible for the authentification via LDAP
is installed. Also the package auth_nds can trigger that error.

"Michael Forster" <admin@muckworld.com> wrote in message
news:3f3c604a@news.userve.net...
>
> "Michael Forster" <admin@muckworld.com> wrote in message
> news:3f3c0373$1@news.userve.net...
> >
Nope didn't work - not running modAuthLDAP and I tried taking the
mod_Authdbm out as well

Mike.

"Michael Forster" <admin@muckworld.com> wrote in message
news:3f3c619f$1@news.userve.net...
>
> "Michael Forster" <admin@muckworld.com> wrote in message
> news:3f3c604a@news.userve.net...
> >
> > "Michael Forster" <admin@muckworld.com> wrote in message
> > news:3f3c0373$1@news.userve.net...
> > >
> Nope didn't work - not running modAuthLDAP and I tried taking the
> mod_Authdbm out as well
Found that it was included in another file suse_addmodule.conf
removed ldap and ndm (or whatever the other problem was)
Now it no longer asks for authorisation, any Idea which module is needed for
default configuration (or is there another directive that is telling it to
look at a specific module for authorisation?

Mike.

Michael Forster <admin@muckworld.com> wrote:
> Now it no longer asks for authorisation, any Idea which module is needed

I use mod_auth, that should be included in every standard
installation/configuration.

Davide

"Davide Bianchi" <davideyeahsure@onlyforfun.net> wrote in message
news:bhj8gl$4ltk$2@ID-18487.news.uni-berlin.de...
> Michael Forster <admin@muckworld.com> wrote:
> > Now it no longer asks for authorisation, any Idea which module is needed
>
> I use mod_auth, that should be included in every standard
> installation/configuration.
>
I had mod_auth loaded but the problem was that I needed to add an
AuthAuthoritative on to the top of my .htaccess file then suddenly it
sprang into life
so I assume somewhere in the wise decision of SuSE they put a global
AuthAuthoritative off in the global settings - I am off to find it now :-)

Thanks for your help

Mike.

"Michael Forster" <admin@muckworld.com> wrote in message
news:3f3dd357$1@news.userve.net...
>
> "Davide Bianchi" <davideyeahsure@onlyforfun.net> wrote in message
> news:bhj8gl$4ltk$2@ID-18487.news.uni-berlin.de...
> > Michael Forster <admin@muckworld.com> wrote:
> > > Now it no longer asks for authorisation, any Idea which module is
needed
> >
> > I use mod_auth, that should be included in every standard
> > installation/configuration.
> >
> I had mod_auth loaded but the problem was that I needed to add an
> AuthAuthoritative on to the top of my .htaccess file then suddenly it
> sprang into life
> so I assume somewhere in the wise decision of SuSE they put a global
> AuthAuthoritative off in the global settings - I am off to find it now
:-)
>
> Thanks for your help
>
> Mike.
>
>
Mike, back in your original setup did you chmod your password file? It
sounds like you can't get past the front door because .htaccess doesn't have
permission to look in .htpasswd.

Wayne Lauman

"WLauman" <wlauman@email.com> wrote in message
news:bib1d108hm@enews1.newsguy.com...
> Mike, back in your original setup did you chmod your password file? It
> sounds like you can't get past the front door because .htaccess doesn't
have
> permission to look in .htpasswd.
>
I had no problem with the permissions on the .htpasswd file, everything is
now working correctly.

The problem was the mod_auth_ldap which SuSE added in their sub custom file
/etc/httpd/suse_addmodule.conf and suse_loadmodule.conf.
I removed the appropriate entries from that but then it failed to prompt,
I then added the AuthAuthorative On
and everything worked correctly.

Mike.