At the same time as the rollout of Spring '13, I'm encountering issues related to High Volume Customer Portal Users: their usernames are now clashing with users in other orgs.
- they must login via a special page identifying the target Org and Portal,
- usernames/emails can be changed at will without requiring verification,
However I was confident that those usernames only had to be unique within my org.
I don't recall seeing this change in the Spring '13 release notes. Can anyone offer guidance? Is this a side effect of the impending release of Chatter Communities?
Edit: what drew me to identify the namespace clash was that I couldn't modify a High Volume Customer Portal User without changing his username first, which was then impossible to change back because it was the same as a non-portal user in another org. You too can sanity check this: try to create a High Volume Customer Portal User with username
email@example.com in a Spring '13 org.
Edit1: raised a case with Salesforce; they reproduced the issue on separate internal test orgs and escalated straight up to R&D. Support from these guys is outstanding. I'll keep you updated.
Edit2: Salesforce have confirmed this is a regression and that they will be releasing a fix for this. Couldn't have asked for a better sanity check than the testing you guys did. Sincere thanks to all.
Edit3: this has been patched by Salesforce in very good time and transparently throughout the process. Portal usernames per-org are restored.