Dave Love <[EMAIL PROTECTED]> writes: > Package: libapache2-webkdc > Version: 3.2.8-1 > Severity: normal
> I've followed the instructions for setting up the package in > README.Debian with no joy. All I get back is http 400, with no other > diagnostics. Do you have any suggestions for debugging, presumably to > improve the instructions to avoid whatever mistake I've made? :-/ > The webkdc module is obviously installed: > # lynx -dump -head https://localhost/webkdc-service > HTTP/1.1 400 Bad Request > Date: Tue, 14 Jun 2005 12:52:27 GMT > Server: Apache/2.0.54 (Debian GNU/Linux) mod_ssl/2.0.54 OpenSSL/0.9.7e > WebKDC/3.2.8 > Connection: close > Content-Type: text/html; charset=iso-8859-1 > I have the <Location /webkdc-service> fragment inside the SSL virtual > server. The server works to serve documents via https (after > considerable confusion with the configuration of the apache2 > package...). I've checked the keytab, acl and keyring files according > to the instructions. The WebKDC never talks to regular HTTP clients, only to a WebAuth server or to a weblogin server. Is a WebAuth server or weblogin server also encountering problems, and do they give similar errors? > Note that this is on sparc -- I don't currently have an x86 system > available to try -- but I doubt that's the problem. Likewise; I've not used it on Debian SPARC, but I know WebAuth works fine on Solaris. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
