emails object versus loginIDs emails object

[keithdever]

Greetings. We ran into at least one case where we're getting "Email Already Exists" response when a username is set instead of e-mail address. What appears to be happening is getMagentoCustomerAndLoggingEmail is getting a list of e-mails from API call where loginIDs parameter is set. I submitted a ticket with SAP requesting logic behind this. We're curious if it's possible to pull list of e-mails based on emails.verified array returned calling getAccountInfo without loginIDs parameter set.

without loginIDs key in getAccountInfo call:
...
"emails": {
"verified": [
"[email protected]"
],
"unverified": []
},
...

including loginIDs key in getAccountInfo call:
...
"loginIDs": {
"username": "[email protected]",
"emails": [],
"unverifiedEmails": []
},
...

In above example, a Gigya user cannot login to any of our Magento sites. Any feedback or assistance is greatly appreciated.