As the title says, I've upgraded to 3.2 and now I get an error in my API perl scripts:
{"message":"Error: Invalid login","code":1}
I've tried to regenerate the apptoken and verified that it's still in the REST API access group.
I've also verified that token login is enabled in the config php file (the same as before)
Has something changed in the API access in the 3.2 version ? Or have I missed some config?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I found the problem, on the User object there's a Scope option now (I don't recall seeing that before), which needs to have REST/JSON in it. Now it works as before.
Last edit: Niclas Eriksson 2025-01-14
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As the title says, I've upgraded to 3.2 and now I get an error in my API perl scripts:
{"message":"Error: Invalid login","code":1}
I've tried to regenerate the apptoken and verified that it's still in the REST API access group.
I've also verified that token login is enabled in the config php file (the same as before)
Has something changed in the API access in the 3.2 version ? Or have I missed some config?
I see this in the errorlog:
authent-token: Scope not authorized code: 400 | TokenAuthLog
I found the problem, on the User object there's a Scope option now (I don't recall seeing that before), which needs to have REST/JSON in it. Now it works as before.
Last edit: Niclas Eriksson 2025-01-14