I finally found out that I needed to install the debian
package
"libapache2-mod-auth-sys-group" with apache2 in
order to keep the
mod_auth_pam functionality of "require group
my-user" that I had grown
used to in apache 1.3. I wish that it had been more obvious
that I
needed to do this, but unfortunately the error message
"configuration
error: couldn't check access. No groups file?" led
me down the wrong
path for about 3 days. I thought that it was referring to
/etc/groups
and that I just had a permissions problem with my
/etc/groups file.
On 3/27/06, Michael Hale <mikehale gmail.com> wrote:
> Hi,
>
> I am trying to upgrade my apache installation to apach2
from apache
> 1.3, but I keep getting the following message whenever
I try to load a
> protected page.
>
> [Mon Mar 27 16:08:33 2006] [crit] [client 192.168.0.5]
configuration
> error: couldn't check access. No groups file?: /rms,
referer:
> https://wiki/
>
> My .htaccess file looks like this:
> AuthPAM_Enabled on
> AuthPAM_FallThrough off
>
> AuthName "RMS Wiki"
> AuthType Basic
> require group developer
>
> This should be handled by mod_auth_pam, which appears
to be loaded
> correctly. At least apache does not complain about the
AuthPam_*
> directives.
>
> I googled around to see if I could find the answer to
this dilema, and
> I did find similar errors with people using all sorts
of different
> authentication mechanisims, like kerbos, but none of
the proposed
> solutions worked for me.
>
> Thanks for any help.
> - Michael
>
------------------------------------------------------------
---------
The official User-To-User support forum of the Apache HTTP
Server Project.
See <URL:http://htt
pd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribehttpd.apache.org
" from the digest: users-digest-unsubscribehttpd.apache.org
For additional commands, e-mail: users-helphttpd.apache.org
|