This project parallels a typical enterprise customer IT environment and the ensuing requirements and restrictions, actually.
Your first and key decision here will be whether you can afford to provide what this customer wants.
If VNC and ssh have been ruled out...
The solution involves figuring out what sort of authentication is in use; is this all running locally, or is the box tied into OD or AD, for instance. You probably already know this detail, but if not... (And the corollary here involves determining if you can attach the Mac OS X Server authentication environment into the larger IT environment. IT likes that.)
If you're running it all locally and not connecting existing distributed authentication, the next step involves creating a sufficiently-simple user interface for the support team or (better) punting this off to the end users and allowing the IT team to "bless" those requests; the less the IT team has to do, the more they'll like your solution. This particularly includes implementing a password reset mechanism or (better) implementing certificate-based logins and (for IT) revocation.
And for IT team, build (or acquiring) https web services interface will likely be your platform of choice here, and with (guessing) IE6 or maybe IE5 compatibility, if you're going to acquire or implement a full IT user-management platform. And within this, you'll probably be calling the [Directory Service command line tool (dscl)|http://developer.apple.com/mac/library/documentation/Porting/Conceptual/ PortingUnix/PortingUnix.pdf] in your script to add users, change passwords, delete users, or other such.