Community user gets "Maximum Logins Exceeded" when performing a login call via SOAP API
Last updated 2017-04-14 ·Reference W-2530634 ·Reported By 5 users
Summary
A standard (CRM) user name is required to be unique across all production and test instances, but a community user name is only required to be unique within a given organization. Thus it is possible to have a standard user with username john.smith@example.com in one organization, and a community user with the same username in a different organization. In this case, SOAP API login calls performed by the community user fail with error "INVALID_LOGIN: User has exceeded the number of allocated logins."
Repro
- Create a community user with same username as another standard user
- Try to login as that user with SOAP. "INVALID_LOGIN: User has exceeded the number of allocated logins" will be returned.
Workaround
Change username to avoid duplicate username with standard user.
Reported By (5)
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.