In theory there is no need for a user module. You could simply have an application connect to the server and issue commands to create/delete/modify user accounts... I'll bet you that 99% of the functionality sought by a user module could be achieved with a new event run at password validation if used in combination with existing events. The new event could create/modify/etc the account and perhaps take over validating the password. If it had to fetch the user info from somewhere, create the account, etc isn't that what the user module would be doing anyway? That's probably the way I'd go... Definitely would still require some sort of background sync routine though in case the central authority was off-line or something...
|