On Thu, 22 Apr 2004 08:36:55 -0500
Charles Thomas [EMAIL PROTECTED] wrote:
For various reasons, our department has implemented a
system whereby we combine Radius authorization (for user
login) with the built-in Apache Basic authorization model
(for management of individual user directory
For various reasons, our department has implemented a system whereby we combine Radius authorization (for user login) with the built-in Apache Basic authorization model (for management of individual user directory privileges via use of an .htaccess file).
We're currently seeing some weirdness
My questions are:Does anyone have any experience using both
systems together?
YES
If so, do you have any configuration tips you'd be willing to
share?
READ BASIC APACHE CONFIGURATION
Can anyone theorize why the wrong error is being
generated when a user doesn't have
From you description it appears it is something in the configuration of Apache
Gary N. McKinney
Network Administrator
Computer Services Dept.
Brevard County Library System
-- Original Message --
From: Charles Thomas [EMAIL PROTECTED]
Reply-To:
Charles Thomas [EMAIL PROTECTED] wrote:
Problem #1: If someone logs in and then tries to access a resource for
which they do not have permission, the server is throwing out an
Internal Server Error (Error code 500) to the browser instead of the
proper Unauthorized (Error code 401).
And
Just a thought... try checking in the httpd-error.log file to see what Apache is
saying is the problem... it may be rather cryptic but should point you in the right
direction
Gary N. McKinney
Network Administrator
Computer Services Dept.
Brevard County Library System
--
My suspicion is this:
Currently they way things are configured the user logs in using Radius and is either a valid user or denied. When the user switches to a directory which is being managed using Apache's Basic Authentication model and an .htaccess file, they are not being re-prompted for a
7 matches
Mail list logo
