Apache Auth exceptions

Hi,

We’ve got a pubcookie (www.pubcookie.org) system running here, which
allows us to do authentication against campus wide windows Active
Directory accounts. Using the simple “Defer to apache auth” option, this
works brilliantly with RT with hardly any effort for “normal” users.

However, I like having a separate “superuser” account to do my setup on
RT, but if I can’t add my own accounts to this central service (we’re a
project as part of a large university).

If I use credentials which aren’t accepted by pubcookie, apache auth
fails and I get a 401 Unauthorized, and don’t get as far as RTs own
login. Is there any way I can set things up to get around this?

Cheers

Carl
Carl Vincent http://www.netskills.ac.uk/ (URL)
Systems, Software, Webmaster 0191 222 5003 (voice)
NETSKILLS - Quality Internet Training 0191 222 5001 (fax)

If I use credentials which aren’t accepted by pubcookie, apache auth
fails and I get a 401 Unauthorized, and don’t get as far as RTs own
login. Is there any way I can set things up to get around this?

I know that several of the apache auth mechanisms have an “is
authoritative” flag. If you turn that off, it should fall back to some
other auth mechanism. So you could set up a chain of authentication
within apache that first checks your campus dictionary, then some local
file-based mechanism, then fails. This assumes your auth mechanism has
such a flag…

Vivek Khera, Ph.D.
+1-301-869-4449 x806

smime.p7s (2.42 KB)