I've started porting the scripts from the old user creation system. Once that's done, I plan to use the token system to create a password resetting page.

For account aging, I plan to add a field in the database of something like date-last-acknowledged. My plan is that we have a job that runs once a day or once a week that sends mail to a user's account when the date-last-acknowledged is at "one year" and then at one month intervals from that. The E-mail will asking them to touch a webpage to confirm they are still using the account. Touching the page will reset the date-last-acknowledged field. When the account has not been acknowledged for 1 year & 3 months, mail will be sent to admin that it is a candidate for deletion. Perhaps more automation that deletes the account will occur instead. We have a year to work that out.

Initially, everyone will start with a date-last-acknowledged of the date I create the column in the table. Potentially, we could use logins and mail access data to kick the date-last-acknowledged but that adds complexity to the system and I don't think an e-mail once a year to click a page, and 3 months in which to do it, is a onerous load on the users. For that matter, we could let the user click on the page any time they like to reset the date-last-acknowledged, even before the mail, to update their timer and they could avoid the mail. However, I like the idea of confirming that a user can actually get mail from their account periodicly.

comments:

WebIt linked to NewUserCreation --key, Sat, 31 Jul 2004 13:08:19 -0700 reply
Since the makeuser script in the NewUserCreation task invokes "webit" to set the permissions in a new user's directory correctly, the WebIt task is now part of the NewUserCreation task.

New User Creation done --key, Tue, 14 Sep 2004 16:14:44 -0700 reply
New User creation is done (has been for a several weeks).