Description
It looks like starting sometime before May 23rd at 5AM, the value for email changed – normally, we received a lowercased version of the users’ email address, which is what would be added on user create since we use SSO integration and the SSO endpoint delivers the email in all lowercase.
However we’re now seeing values in all sorts of odd casing (which is fixable) as well as values like:
user@domain.edu,User@DOMAIN.edu
Which is also fixable but very perplexing, since no changes to your API have been recorded as of late. I’m worried that for the multiple email situations, I’ll end up with two wildly different emails.
Error
No error, just unexpected values.
Which App Type (OAuth / Chatbot / JWT / Webhook)?
JWT
@alexmayo Okay, that explains the first problem I had, but what about the second, where there are multiple email addresses in the email field? Are they just caseless and cased versions of the same value?
I understand from my support case engineering was considering rolling this change back. This appears to have already occurred as the symptoms are no longer reproducible.
I’m sorry that you encountered this issue when using our API! This was related to an issue that we identified with our latest update. As you mentioned, our engineering team has since rolled back this change and the issue should now be resolved.
Please reach out if you see any further instances of this.