The ISP I'm working for has been handling domain registrations asynchronously for some
time now.
We log domain registration requests in a database, wait for the client's fax,
authorize the registration through a web interface and then the backend will proceed
with the actual registration (send email, wait for reply, etc. -- this is both for
network solutions and for the italian NIC).
I'm attempting to integrate OpenSRS into our backend by calling into the SRS server
from our backend, and possibly providing a customized manage.cgi.
I actually have a pretty simple perl sub that will fish user data from our database
and register the domain on the test SRS server.
My problem now is how to create users on the SRS server. I was thinking of
automatically generating a username and a password, and notifying the user about it,
and maybe reuse the same username and password if the user wants a new domain. However
if the user changes the password through the manage interface I'll no longer be able
to do it.
Perhaps I should ask about domain/user creation semantics: can two user "joe" exists
at the same time if they're associated with two different domains?
This would allow me to request a username and password that I only actually create on
the SRS server in a later session (possibly a few days later).
Otherwise I'm kind of stuck.
Thanks for any help,
Duncan