11

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.

I'm aware that Portal Users are almost first class citizens: they have Session Ids, can perform JavaScript Remoting, can be given permission to make API calls etc, but:

  • 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 protected] 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.

dev org clash

Improve this question
15
  • 2
    Could you provide a bit more detail in your question about how you've identified that you had user accounts which clashed with another org? (as opposed to within your own org)
    – Mark Pond
    Feb 7, 2013 at 21:46
  • 1
    Are you 100% sure you don't have that user in your org?
    – PepeFloyd
    Feb 7, 2013 at 22:22
  • 2
    I panicked a little reading this. I tried creating a user with the username you provided and it was fine. Do you have just one org? Are you sure you do not have another user with this name?
    – Richard N
    Feb 7, 2013 at 22:23
  • 2
    I tested with a Winter13 DE sandbox and it worked (as you expect). I then created a partner org and unfortunately it didn't provide me the ability to specify the version I was interested in and it was created in Winter12 also... so, I can't yet test this further myself. When you click the 'View Users' button when viewing the High Volume Customer Portal profile, does it show another user with that username in the list?
    – Mark Pond
    Feb 7, 2013 at 22:44
  • 2
    @user31 - I can confirm that this is happening for me on my Winter '13 DE (na14). I can create a portal user in my org with [email protected] as the username, but I cannot create a portal username that has the same username as one of the regular names in my org, and I cannot create a regular user that has the same username as one of my portal users. FYI: I don't have a lot of users in my DE, so I can just view all of them in a users list view easily.
    – Peter Knolle
    Feb 7, 2013 at 23:20

1 Answer 1

Reset to default
6

As user320 mentions in an update at the bottom of the question, this was a regression in Spring '13. Salesforce fixed the issue in a patch release during the week of Feb 11 2013.

Improve this answer
0

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .