Re: REST API authentication issue
Paul Timms
9-14-22
Version 2022-08-01 seems much better in respect of the REST API. We still have one issue with OAuth2, which I believe has been reported and assigned to Erik. During the OAuth2 flow, there's a recommended parameter called "state", described as:

state (recommended)
The state parameter is used by the application to store request-specific data and/or prevent CSRF attacks. The authorization server must return the unmodified state value back to the application.



If the redirect URL is sending this state parameter, it may require it to be sent back from the authorisation server. Currently, the Standard ID authorisation server doesn't support this and sends nothing back, resulting in a failure. As the state parameter is becoming more commonly used, it's important that this functionality is added quickly.
Leave Comment
You can subscribe to notifications for this post by selecting the 'star' icon on the top right corner of the post.
Latest Posts
Paul Timms
I've found an issue which I'm trying to find the best way to resolve. An integrated proof of delivery system sends two pieces of data to the SERP API, in two separate calls - let's c...
17:59 20 Feb 2026
Andis Blicāns, Grasko
There are some topics in this Q&A related to this question, but none of them is about Idle users - Concurrent or Named. If timeout minutes are specified in Optional Features, then all idle users are...
15:53 18 Feb 2026