Hi
I have a question about AuthbyPolicy function
Supposing that we would like to use AuthByPolicy x and we have multiple
AuthBySql (1,2 3) after that ,each one with an AuthSelect attached to it
that has check and reply items.
I want to accept the call only when all AuthBySql are accepted/passed
I understand that the AuthSQLStatement allows arbitrary sql statements
to be run at sundry points in the request process. Is there any way to
access the results of those AuthSQLStatements?
For example, if my AuthSQLStatement executes: select data1, data2,
data3 from table_XX where data1 = "ABC
We are currently using Handlers to authenticate using Called-Station-ID. One of our
proxy customer is asking that we add a default realm to all of his users that don't
use a realm. If they have a realm, then he would like that username passed along
'as-is'.
This seems to be something that s
Hello Kevin -
You will need to write a PreAuthHook for this Handler, as a simple
RewriteUsername will not work.
There are some example hooks in the file "goodies/hooks.txt" in the
Radiator 3.5 distribution.
regards
Hugh
On Tuesday, Dec 31, 2002, at 05:16 Australia/Melbourne, Kevin McKee
w
Hello Seung Park -
There is no mechanism currently to access the results of an
AuthSQLStatement later during packet processing.
This is why I suggested a PostAuthHook to post-process the results of
the AuthSelect/AuthColumnDef in my other mail.
Of course, you can also run SQL statements direc
Hello Marius -
You would use an AuthByPolicy ContinueWhileAccept.
Ie:
# define AuthBy clauses
Identifier CheckSQL1
.
Identifier CheckSQL2
.
Identifier CheckSQL3
.
.
# define Realms or Handlers
AuthByPolicy ContinueWhileAccept
AuthBy CheckSQL1
AuthBy CheckSQ
The attached is our postauthhook file which we use to see if the user
has exceeded their quota of usage, this is calculated on a rolling 30
days. The problem we have is that when a user has used 150% or more we
are trying to send a reject, and due to safety in the script we return 1
second session
Hello Steve -
I suspect the problem is due to an internal change in the replyTo()
call.
It should look like this (in recent versions of Radiator):
# Reply to the Client that sent the request.
$p->{Client}->replyTo($p);
return;
BTW - for clarity, I would suggest using the correct Post
Maybe I should have explained the server setup more ...
The server is acting as a proxy, but it holds the accounting locally in
MySQL and authenticates from an icradius server until I have time to
merge 5 separate servers into 2 failover with 1 management solution.
Steve.
On Tue, 2002-12-31 at 0
Hello Steve -
Ah right.
In that case, just to make my life easier perhaps your subject line
could refer to a "ReplyHook"?
;-)
cheers
Hugh
On Tuesday, Dec 31, 2002, at 12:02 Australia/Melbourne, Steve Wilson
wrote:
Maybe I should have explained the server setup more ...
The server is act
10 matches
Mail list logo
