We have an oauth2 authorisation with client Id , client Secret & scope to connect to an api. We already have a connected system configured for this . This is working fine & we are getting expected response from api.
Traditionally in our organisation we have a process model per application which runs every 60 mins which generates the token & writes to the token table. This token from db is accessed and set in the the header of the request as Authorization: Bearer ******. But it seems our code is working even if that Authorization header is deleted from the integration. It seems the connected system is adding the Authorization header to the integration request and the process model to token generation is not required at all.
Does this a ring a bell ?
Discussion posts and replies are publicly visible
For Oauth , Appian Generates the new token automatically for the Client Credentials Grant as long as it gets the 401,403 and 404 Error code back to that when Token Expires , From What I understand you already have the error code correctly sent that is the reason it generates new token , so you may not need the process model token generation again , We face some issues in the Gateway that during token refresh after an hour it send 200 success with token expired issue , In that case Gateway team fixed the 401 error rather than 200 success and it started generating the new token and being used for the integration again . Work scenario we keep a timer event to again run the integration one more time for failed cases . I hope this answers your question
OAuth 2.0: Client Credentials Grant - Appian 24.3
Once the connected system has an access token, future requests will be granted until (1) the external application revokes permission, or (2) the access token expires.Appian considers an access token to be revoked or expired when it's used to call an integration and the integration returns a status code of 401, 403, or 404. At that point, Appian will automatically call the Token Request Endpoint to fetch another access token with the credentials from the connected system. If that call is successful, Appian will use the new access token to automatically retry the integration call
401
403
404