Hi Lindsay and everyone, We are testing the fix for .BIZ and .US unlocking. The code was promoted last night. Yesterday we attempted to add the fix in the afternoon, but had to roll it back for further development work. We hope that the fix we have now will resolve it for you and your customers.
Once it is confirmed, I will respond on list and update the status page. Thanks, Heather On Mar 31, 2008, at 6:49 PM, Lindsay H wrote: We noticed this a while ago too and reported it to Tucows. I had hoped it was fixed by now.. If it's any consolation though, when your customers get upset and try to unlock their domains to transfer out and leave they will not be able to! Thanks to the registry errors produced trying to unlock certain domains. I was told an emergency fix would be in place Friday evening but that appears not to be the case. - Lindsay On Mar 31, 2008, [EMAIL PROTECTED] wrote: There seems to be a problem with the profile username and password info returned for some domains. The system is returning out of date information. This happens using both the "get username and password" link in the RWI, and with the get_user_access_info API call. In these cases, the username and password returned by the RWI and API can't be used to log in to the MWI, nor can they be used to set a cookie in the API, because they aren't valid credentials. But if the user logs in to MWI with their (correct) credentials, and changes their password, this fixes the problem; the correct profile information then appears in the RWI, and is also returned by the API. It seems as though the profile information returned by the RWI and API, and the profile information used for authentication, are stored in different databases, and at some point, some profile changes didn't replicate, so the two databases are now out of sync. Whatever the reason, the profile information returned by RWI/API for some domains is out of date. We first encountered this a few months ago and chalked it up to a fluke, but it's happened several more times since then, and I'm dealing with another case right now. Tucows: please contact me off-list and I'll provide you with an example domain that's affected by this problem. Alex _______________________________________________ domains-gen mailing list [email protected] http://discuss.tucows.com/mailman/listinfo/domains-gen _______________________________________________ domains-gen mailing list [email protected] http://discuss.tucows.com/mailman/listinfo/domains-gen Heather Leson Customer Communications Specialist Tucows [EMAIL PROTECTED] _______________________________________________ domains-gen mailing list [email protected] http://discuss.tucows.com/mailman/listinfo/domains-gen
