Hello John,
if they try to authenticate with TimLeft less than 0, I would expect to see
thme rejected with a DEBUG message like:
User $name has no more time left
Is that what you are seeing?
Cheers.
----------------------------------------------------------------------------
---------------
Mike McCauley [EMAIL PROTECTED]
Open System Consultants +61 3 9598 0985
Mike is travelling right now, and there may be delays
in our correspondence.
-----Original Message-----
From: John Vorstermans <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Thursday, October 28, 1999 5:10 PM
Subject: Re: (RADIATOR) TimeLeft
>Hi Hugh.
>
>Yes, thanks for that, the TimeBanking option helps and I can confirm that
>the customer now does get cut off when their time goes into the negative.
>
>However they can then dial-in again and get connected without a problem and
>stay on-line for as long as they like. That is, if the Timeleft is a
>negative number.
>
>Is this the correct action for Radiator? That is, to accept authentication
>when Timeleft is a negative number or are you not concerned with this and
>only use this as a method of when to disconnect a user?
>
>It seems to me that it would be useful to not allow authentication when the
>number is a minus/negative and return an error message to that effect but
>perhaps I have missed a point?
>
>I'd be keen to here your point of view Hugh?
>
>Cheers and thanks for your help so far.
>
>John
>
>
>
>At 14:00 28/10/99 +1000, you wrote:
>
>>Hi John -
>>
>>On Tue, 26 Oct 1999, John Vorstermans wrote:
>> > We have "Block User" set to Y in Platypus and the time gets subtracted
>> just
>> > fine from the users total after a disconnect. However we are using
AuthBy
>> > EMERALD rather then AuthBy Platypus which may be the problem?
>> >
>>
>>Ahhhh - of course, that changes things.
>>
>> > AuthBy Emerald is what Platypus recommend when running Radiator as this
>> > allows us to manage the User Attributed easily from within Platypus.
Does
>> > this mean I should look at a change in Emerald.pm?
>> >
>>
>>I've checked the code, and as you say, AuthEMERALD decrements the time
left
>>correctly. The code also respects the "TimeBanking" parameter to restrict
user
>>time limits - have you tried that?
>>
>><Handler ...>
>> <AuthBy EMERALD>
>> TimeBanking
>> ....
>> </AuthBy>
>></Handler>
>>
>>hth
>>
>>Hugh
>>
>>
>>--
>>Radiator: the most portable, flexible and configurable RADIUS server
>>anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
>>Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8,
>>NT, Rhapsody
>
>--
>John Vorstermans || We are what we repeatedly do.
>Technical Manager || - Aristotle
>Actrix Networks
>
>===
>Archive at http://www.thesite.com.au/~radiator/
>To unsubscribe, email '[EMAIL PROTECTED]' with
>'unsubscribe radiator' in the body of the message.
>
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
