I wanted to ask, the value topped up for a permanent user under the time profile, does is stop counting after the specified time or does the counter stop when a user logs out.
for example if a user tops up 1 day, at 7pm, will there time expire tomorrow at 7 pm or will the counter stop when the user logs out i.e. 5 hours today, 4 hours tomorrow, 6 hours the next day and so on and so fourth.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have been doing a bit of reading and from what i get is that the time profile in Radiusdesk is set to "Max-All-Session" which is accumulative time. I want to change this to "Access-Period" so that a users account expires at a fixed date since the last top.
E.g. A one week top expires 7 days from the date of topup. Is this possible???
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There has been provision made for this by the days_to_use field in the top-ups table.
The code around it however was never completed. I did something similar for people on YFi a few years ago.
So what happens a person does a CC x-action and based on the number of days the perosn choose their account expiry date is extended each time.
So it is a matter of adding the plumbing around the add code to see if there is a days_to_use provided and if so it will ADD those days to the current expiry date of the account.
Cheers
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Dirk,
Is that anyway we can set the Expiration date and time for individual permanent user based on rather than set in profile component
YYYY-MM-DD HH:MM:SS? which i know is Expiration attribute. Compare to current setup is only date in basic info.
Temporary solution is to manual inject attribute into radcheck table
for eg. [username] Expiration := 20 Nov 2014 07:00:00
so the username will timeout when that time reach.
Cheers
Last edit: ryan low 2014-11-10
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Replys, yeeeee. So days to use it is, I dint quite get what days to use was, will see how current structure can be implemented, while we wait for better plumbing, :-)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I wanted to ask, the value topped up for a permanent user under the time profile, does is stop counting after the specified time or does the counter stop when a user logs out.
for example if a user tops up 1 day, at 7pm, will there time expire tomorrow at 7 pm or will the counter stop when the user logs out i.e. 5 hours today, 4 hours tomorrow, 6 hours the next day and so on and so fourth.
I have been doing a bit of reading and from what i get is that the time profile in Radiusdesk is set to "Max-All-Session" which is accumulative time. I want to change this to "Access-Period" so that a users account expires at a fixed date since the last top.
E.g. A one week top expires 7 days from the date of topup. Is this possible???
Anyone???? :(
Hi Barnabie,
I suggest you to read this link:
http://www.radiusdesk.com/technical_discussions/principle_profile
Hi Barnabie,
Sorry for the slow response.
There has been provision made for this by the days_to_use field in the top-ups table.
The code around it however was never completed. I did something similar for people on YFi a few years ago.
So what happens a person does a CC x-action and based on the number of days the perosn choose their account expiry date is extended each time.
So it is a matter of adding the plumbing around the add code to see if there is a days_to_use provided and if so it will ADD those days to the current expiry date of the account.
Cheers
Dirk,
Is that anyway we can set the Expiration date and time for individual permanent user based on rather than set in profile component
YYYY-MM-DD HH:MM:SS? which i know is Expiration attribute. Compare to current setup is only date in basic info.
Temporary solution is to manual inject attribute into radcheck table
for eg. [username] Expiration := 20 Nov 2014 07:00:00
so the username will timeout when that time reach.
Cheers
Last edit: ryan low 2014-11-10
Replys, yeeeee. So days to use it is, I dint quite get what days to use was, will see how current structure can be implemented, while we wait for better plumbing, :-)
Hi, any update on the days_to_use feature with the new radiusdesk (cakephp3, freeradius3 etc). Is the "plumbing" done