Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
The version field defines the version of the software the bug was found in. [ID: 1154637]
View issue level access limits(Press Alt + Right arrow for more information)
Unintended behavior
View staffing
Description
We've run into a few different issues utilizing these API's since updating to 3.8 and so I tried to capture the simplest example of our issue here. This kind of felt like
What steps will reproduce the problem?
1. Create an account where a user has both a primary and secondary email address
2. Utilize the curl API to try and retrieve information for the user with their secondary email
For example:
```
curl -u geissonator:<key>
{"registered_on":"2016-06-13 14:18:59.000000000","_account_id":1000004,"name":"Andrew Geissler","email":"geissonator@yahoo.com","secondary_emails":["andrew@geissonator.com","null","openbmcbump-github@yahoo.com"]
```
This works fine to get the account info:
```
curl -u geissonator:<key>
```
But if I try the secondary email, it can not find the account:
```
curl -u geissonator:<key>
Account 'andrewg@geissonator.com' not found
```
What is the expected output?
Prior to 3.8, you could look up users with any email address associated with their account.
What do you see instead?
Secondary email addresses can not be utilized to look up accounts anymore via the REST API.
Please provide any additional information below.
This was not an issue with the 3.7 or prior releases.