Recent changes to api requests?


(Carlo Kok) #1

Since a day ago or so (pretty sure i updated yesterday morning) my api requests started failing (using the same api token and usename which is still in the settings), it fails with 403:
“Non ti è consentito visualizzare la risorsa richiesta. Il nome utente o la chiave API non sono validi.”

Which is double curious, as my system is set to EN_US, my site is set to English (without the option to change it). What am I doing wrong?


(Jay Pfaffman) #2

That does sound strange. What endpoint are you accessing?

Also this might be related:


(Sam Saffron) #3

Do you have user locales enabled? maybe it is coming from there, do all endpoints give you a 403 can you try a different one.

What if you generate a new key does that work?


(Carlo Kok) #4

I found what it was. I had a key for “all” users, but somehow my “RemObjects” user got renamed to RemObjects1.

https://talk.remobjects.com/u/remobjects1/

Oddly,
https://talk.remobjects.com/u/remobjects/

doesn’t work but if I try to rename that back it says “username in use”.

The pgsql doesn’t db doesnt’contain a remobjects user anymore either.

We do have a RemObjects group. Could it be that discourse somehow ran a “rename users that match a group name” task?


#5

Yes, there is a new weekly job to rename usernames that clash with a group name:


(Carlo Kok) #6

The “default to italian” was kinda odd though (I do have user locales enabled, but curl doesn’t seem to pass Italian anywhere)


#7

I suspect this is happening because the target user has Italian as their UI language. I’d look in their /preferences/interface or try a different user.


(Carlo Kok) #8

The user in question didn’t exist (RemObjects was renamed to RemObjects1) and I did my request as RemObjects.