Encoding errors since new OAuth upgrade

[Roger Hyam]

Creating a thread incase anyone else is having this issue. I've written to support about it too.

We are having issues with the new OAuth upgrade since the software upgrade on 8th April 2026

Name strings that are returned by the calls have accented characters replaced with question marks. There is something going on with the encoding.

I added an acute and umlaut to my name for testing and this is the JSON we get back on success.

{"access_token":"008ce02e-1c51-470f-8420-fb87d8936985","refresh_token":"0a454d21-69f0-429c-accb-c9439b5e25bd","scope":"/authenticate","name":"Rog�r Hy�m","orcid":"0000-0003-4581-1379","token_type":"bearer","expires_in":631138518}

This is a growing issue for us as it mangles our data each time an author logs in. Is anyone else having this issue? Is it us?

[m.villalo...@orcid.org]

Hi Roger,

Thanks for bringing this to our attention.

Our technical team has implemented a fix, which has now been deployed to production.

If the issue persists, please let us know. Thanks!

[Roger Hyam]

It works for us now!

Thank you.