[Pugged] .htaccess & DB

[Steve Langasek]

--N1GIdlSm9i+YlY4t
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Sep 12, 2002 at 01:35:33PM -0500, Tim Perdue wrote:
> On Thu, Sep 12, 2002 at 01:12:15PM -0500, Steve Langasek wrote:
> > On Wed, Sep 11, 2002 at 06:13:43PM -0500, Tim Perdue wrote:
> > > Has anyone controlled access to apache directories by looking up perm=
issions
> > > in a database? I'm sure it's been done many times, but I don't recall=
 seeing
> > > it anywhere.
> >=20
> > > Essentially, it would be like making your .htaccess file a simple shi=
m that
> > > looks into a database structure for username/pass.
> >=20
> > > Any pointers would be helpful/

> > Something like this?

> > $ apt-cache search mod-auth.*sql
> > libapache-mod-auth-mysql - Apache module for MySQL authentication
> > libapache-mod-auth-pgsql - Apache module for PostgreSQL authentication
> > $

> > Never used either of them, myself; I'm more inclined to use mod_auth_pam
> > or mod_auth_krb5...

> Hmm - this is going to be hosted at an ISP, so I don't know if modules wi=
ll
> work. I may have to generate the .htaccess files using a script of some s=
ort,
> although that's ugly as hell.

Well, the only way to change the authentication source for .htaccess is
if you have other Apache authentication modules installed.  Otherwise,
you can dynamically rewrite .htpasswd, or you can do your authentication
directly in PHP.

Steve Langasek
postmodern programmer

--N1GIdlSm9i+YlY4t
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9gOHkKN6ufymYLloRAiVTAJsHwRsy/n1HNvbGLqbabtTgly4DzgCgrD0f
KiRF24uqnLRpUMsNn5XNRis=
=2T0Q
-----END PGP SIGNATURE-----

--N1GIdlSm9i+YlY4t--