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
Lilian Wanyoike
Hi, We have a customer who creates on account receipts against a customer account. Another team is required to allocate these receipts to specific invoice records. Prepayments will not work as t...
15:49 6 Oct 2025
Piotr Wycichowski
Hi! I am not able to run SERP client on Mac (Sonoma), when the folder is outside of Applications. When and why it happens? I know, that some users with the same system haven't such problem. ...
14:54 19 Sep 2025