Hi all,
We have a connected system with OAuth 2.0 Client Credential Grant. From the connected system we can Authorize with no error. Now, the token we get is valid for 24 hours. The problem is, after 24 hours, the integration calls fail with Authorization error. And when I go to Connected System and click on Authorize and run the integration again, it works perfectly. Does anyone know why this may be happening? I checked and the security of the integration and connected system is set properly.
Thanks!
Discussion posts and replies are publicly visible
This was a while back - have you been able to find a solution?
Seeing a similar thing in one of the integrations - if I were to guess - when we call the resource server, then Appian expects a 401/403 response from the integration call, but most likely the resource server API returns another code, e.g. 200 (success) code with an HTML page trying to redirect to authorize. The issue with this would be that this does not prompt Appian to retrieve a new Bearer access token from the Authorization server
RFC 6749 https://www.rfc-editor.org/rfc/rfc6749.txt section 1.5 covers Refreshing an Expired Access Token
Just curious - what system are you connecting to?
Is there any solution for this while using client credentials grant after few hours it looks to me it says request rejected with 200 success message , after authorise it works well and then if it is not used for some time similar things repeat , if it returns 200 will it get new token if not what is the best way to authorise it again automatically and fix this
You'll probably need a custom CS for this. Standard HTTPS connected system doesn't support refresh tokens AFAIK.
Thanks Mathieu , it would be if you could explain more abt the solution what you are refering here how do we create such in Appian , I thought it is generally usage for CS to use the client credentials grant with regular refresh , is there any existing bug in the system or something else , whether this error is invalid code generated or Appian not handling this responds properly and generate new refresh token , pls advise .