Bug#313593: libapache2-webkdc: no joy following the instructions
Russ Allbery [EMAIL PROTECTED] writes: 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? Ah. I obviously haven't read enough. I thought I needed to get webkdc going first and wanted to check it was actually responding, as I had trouble with apache2. I guess this can be closed, but I'll try to get everything working and let you know about possible useful changes to the readmes c. I should have said thanks for packaging it in the first place, which helps choose versus cosign. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#313593: libapache2-webkdc: no joy following the instructions
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. I don't get anything relevant in the logs (even with `WebKdcDebug on' in the config and making the server logging level `debug'). I don't have any other ideas, not knowing a lot about apache. Note that this is on sparc -- I don't currently have an x86 system available to try -- but I doubt that's the problem. -- System Information: Debian Release: 3.1 Architecture: sparc (sparc64) Kernel: Linux 2.4.26-sparc64 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages libapache2-webkdc depends on: ii apache2 2.0.54-4 next generation, scalable, extenda ii apache2-mpm-worker [apache2 2.0.54-4 high speed threaded model for Apac ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii libcomerr2 1.37-2sarge1 common error description library ii libcurl37.13.2-2 Multi-protocol file transfer libra ii libkrb531.3.6-2 MIT Kerberos runtime libraries ii libsident0 3.4-3Shared libraries to do S/Ident aut ii libssl0.9.7 0.9.7e-3 SSL shared libraries ii libwebauth1 3.2.8-1 Shared libraries for WebAuth authe -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#313593: libapache2-webkdc: no joy following the instructions
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]
