You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by Michael McLagan <Mi...@Linux.ORG> on 1998/07/12 13:43:37 UTC

mod_auth-any/2598: mod_auth_dbm requires mod_auth -- not documented?

>Number:         2598
>Category:       mod_auth-any
>Synopsis:       mod_auth_dbm requires mod_auth -- not documented?
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Sun Jul 12 04:50:00 PDT 1998
>Last-Modified:
>Originator:     Michael.McLagan@Linux.ORG
>Organization:
apache
>Release:        1.3
>Environment:
Linux 2.0.34, GDBM 1.7.3, PERL 5.004, RedHat 5.0
>Description:
Using:

---

AuthType Basic
AuthName "Site admin"
AuthDBMUserFile sitepasswd
AuthDBMGroupFile sitepasswd

<Limit>
order deny,allow
allow from all
require valid-user
</Limit>

---

and loading only mod_auth_dbm, the browser shows "Internal Server Error"
while error log shows :

[crit] configuration error: couldn't check access.  No groups file?: /admin/

Even after deciphering the dbmmanage problem (submitted earlier) didn't
solve this.  Creating a special group file based on the format requested in
the docs didn't resolve this.

The only way I was able to access this area was to modify the config to include
mod_auth, and USR1 the server.

This allowed me to use the same old passwd file, despite it not having group
info in it.
>How-To-Repeat:
You should be able to repeat it by creating a server conf with just mod_auth_dbm
included, and us the above listed .htaccess file.  It should fail as indicated.
>Fix:
A) Document it

    and/or

B) Fix the reason it fails.
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <ap...@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]