It is my understanding that if a customer has an email address in the database, but it is not associated with a web login (in T_CUST_LOGIN), then that customer will be unable to use that email address to register for a new web login (due to the preexisting address) and will also be unable to recover the account online (due to the lack of an actual login to recover).
Assuming that is true, would anyone recommend a good workaround for this situation? The best I can come up with is to create a procedure that runs periodically and creates web logins for email addresses that haven't already been associated with a login. This seems pretty clunky, though. Thoughts?
We have done something similiar before. But there is always a chance that the id has not yet been created. Maybe you can do something with forgot password/login and call a custom proc to create the missing user id.
Jon
We are having a similar discussion about temp logins. I'm curious--when you are creating a login using their email address, are you flagging the login as temporary or flagging the password as temporary?
I would think that you would want the logins to be permanent, but the passwords temporary. The users can then just update their passwords over time.
Thanks,
Patrick
Technical Project Analyst The Pittsburgh Cultural Trust 803 Liberty Avenue Pittsburgh, PA 15222 fitzgerald@pgharts.org w 412-325-7061 c 646-434-8955