Your message dated Mon, 31 May 2010 00:27:17 +0200
with message-id <[email protected]>
and subject line Fixed in libapache-mod-auth-radius 1.5.8-1
has caused the Debian Bug report #562113,
regarding mod_auth_radius 2.x missing the ability to use different servers in
different directories
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
562113: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562113
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libapache2-mod-auth-radius
Version: 1.5.7-8
Severity: normal
Rewriting subject to 'libapache2-mod-auth-radius: This modules' parameters,
while determined syntactically correct by apache2, accomplish nothing. When
setting up a standard vhost in apache2, with intent to use RADIUS for
authentication, parameters are entered as described online, involving these
parameters in my vhost and IfModule configurations:
#### VHost config
AuthType Basic
AuthName "RADIUS auth"
AuthBasicAuthoritative Off
AuthRadiusAuthoritative on
AuthRadiusCookieValid 1
AuthRadiusActive On
Require valid-user
##IfModule config in /etc/apache2/apache2.conf
LoadModule radius_auth_module modules/mod_auth_radius.so
AddRadiusAuth ip_addr:port presharedsecret 10:5
AddRadiusCookieValid 1
####
Observing network traffic on the RADIUS Apache2 client yields absolutely
nothing related to an attempt to contact RADIUS.
Logs on working RADIUS server indicate no opened connections from client. Not a
peep in our logs, period.
Thoughts? Alternatives? I've tried the AuthRadiusBindAddress parameter as well,
thinking maybe it didn't implicitly know that it should use the one IP
configured on the system. No change.
Thanks
J
-- System Information:
Debian Release: 5.0.3
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-1-686 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages libapache2-mod-auth-radius depends on:
ii apache2.2-common 2.2.9-10+lenny6 Apache HTTP Server common files
ii libc6 2.7-18 GNU C Library: Shared libraries
libapache2-mod-auth-radius recommends no packages.
Versions of packages libapache2-mod-auth-radius suggests:
ii apache2-mpm-prefork [apa 2.2.9-10+lenny6 Apache HTTP Server - traditional n
ii freeradius [radius-serve 2.0.4+dfsg-6 a high-performance and highly conf
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.5.8-1
Hi,
The documentation is now completely updated for the new-style Apache
configuration so there should no longer be any ambiguity as to how to
set the module up - using 'AuthBasicProvider radius'.
Since there was no other reply regarding your specific problem, I'm
closing the bug now. Thanks for reporting.
--
2. That which causes joy or happiness.
--- End Message ---
