(RADIATOR) Adding reply- and check attributes after Access-Accept

[Rickard Gunnarsson]

Hi,

this is my problem: I've got a number of pre-generated user accounts in an
SQL-database. Whenever a user uses his account for the first time, the
account should be valid for 24 hours. To not complicate things, we can
assume there are no check- or reply attributes by default.

My idea was to check whether a first successful authentication has occurred
and if so add a reply attribute like Session-Timeout=86400 (24hrs) to the
reply packet.
I would also need to update my database to add the check attributes
Time=[now-(now+24hrs)]  and Expiration=[now+24hrs] and a reply attribute
like Session-Timeout="until Time". This would give the correct behaviour for
future authentications the following 24 hours.

I intended to solve this by using the PostAuthHook, checking if the
Session-Timout attribute was present in the reply packet to decide if the
account is used for the first time, and if so adding the Session-Timeout to
the reply packet and updating my database.

I guess this would work, but it doesn't look as an optimal solution to me
from a performance point of view.
Anyone got an idea of a better way of solving my problem? Possibly using an
SQL trigger or function called by AuthSQLStatement or something else?

Regards,

Rickard



===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.