<Directory /var/www/seqta/demo/ta/>
# AUTH START
AuthName “Kerberos Login”
AuthType Kerberos
KrbServiceName HTTP
Krb5Keytab /etc/apache2/master.keytab
KrbAuthRealm SEQTA-TEST.LOCAL
KrbMethodNegotiate on
KrbMethodk5Passwd on
KrbSaveCredentials on
require valid-user

Options +FollowSymLinks +Includes
XBitHack on
</Directory>

<Location /seqta>
ProxyPass http://localhost:8080/demo/seqta
ProxyPassReverse /
ProxyPassReverseCookiePath /demo/seqta /
Allow from all
</Location>

I’ve been struggling to get a similar situation working for a directive but everytime I see the module loading for a proxied URL the request->user field is NULL! A snippet of the config is below, and I’ve taken the code from “threebit” and made the above changes.

I thought that perhaps things had changed, but from what I can see the “fixup” hook is still correct (mod_proxy_http is in the handler phase, and mod_auth_kerb is still in the auth/security phase). Any suggestions would be welcome!

#– SNIP –

# AUTH START
AuthName “Kerberos Login”
AuthType Kerberos
KrbServiceName HTTP
Krb5Keytab /etc/apache2/master.keytab
KrbAuthRealm TEST.LOCAL
KrbMethodNegotiate on
KrbMethodk5Passwd on
KrbSaveCredentials on
require valid-user

Options +FollowSymLinks +Includes
XBitHack on

ProxyRequests off

ProxyPass http://localhost:8080/test
ProxyPassReverse /
ProxyPassReverseCookiePath /test /
Allow from all

#– SNIP –

I haven’t used the “Fixup” hook because the module I was using is setting the REMOTE_USER *after* the fixup phase, during the handler. Therefore the module is ugly and depends on the order on which modules are loaded, this is the only solution I see for my problem. Once again, many thanks for your article.

Many thanks for this article, I’m facing the same problematics with mod-auth-openid (an openid authentication module for apache), and I think I’m going to write a little module for it