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
David Delač
Hi Gastón, Please report a bug in our issue tracker and attach test database that you can repeat this in so I can have a look. Paste subject here once done...
09:46 14 May 2025
Paul Timms
From what I've read, using these will store the updated records in memory and then write them to the database in bulk, instead of each record writing to the database in turn. So perhaps there&apo...
17:53 29 Apr 2025