Skip to main content
A
aksharc
May 7, 2021
Question

Connected System with Client Credential Grant

  • May 7, 2021
  • 14 replies
  • 0 views

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!

14 replies

meelisk648
meelisk648
June 11, 2021

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?

    A
    aksharcAuthor
    June 14, 2021

    No. For now, what I did is to create a process model which fetches the token every few hours and save it on the constant. I raised an enhancement request as well with Appian.

    We have internal OData API servers which uses OAuth authentication!

      stefanhelzle0001
      stefanhelzle0001
      June 14, 2021

      I think a server returning a 200 code in case it cannot authenticate the user is just wrong and violates the HTTP protocol. I mean, we are talking about APIs here. How is the chance that a user is hitting the API endpoint with a browser?

        Terms & ConditionsAccessibility statement