Integration fails when token expires

RE: Integration fails when token expires

venkatesanr1106 — Wed, 11 Dec 2024 16:02:35 GMT

I am exactly facing this issue , pls let me know , what Is the resolution how API fix the issue how they change this to 401 errors code ,whether Appian gen new token after that . Any help is much appreciated ?

RE: Integration fails when token expires

Stefan Helzle — Wed, 10 Jan 2024 10:54:26 GMT

👍

RE: Integration fails when token expires

Nupoor Gupta — Wed, 10 Jan 2024 10:50:55 GMT

It's fixed, issue was from the API team.

RE: Integration fails when token expires

Stefan Helzle — Wed, 10 Jan 2024 09:51:07 GMT

Because Appian would manage that automatically.

https://docs.appian.com/suite/help/23.4/oauth_client_credentials.html#access-token-expiration

But implementations and configurations vary .... talk to the teams developing the APIs and managing the access management systems.

RE: Integration fails when token expires

Bilal Qasim — Wed, 10 Jan 2024 09:43:24 GMT

How about calling a get access token integration object and writing the access token to a table. When running the above integration you get the latest row from the access token table. If the integration fails then get a new token, write to the db and query the table? See example below:

RE: Integration fails when token expires

Harshit Bumb (Appyzie) — Wed, 10 Jan 2024 08:21:37 GMT

Post and Get are two different types and depend on the API. We cannot choose between the two. This has to be the same as the API configurations.

RE: Integration fails when token expires

Rishikesh Raj — Wed, 10 Jan 2024 08:07:50 GMT

500 is for Internet server error at server side. Might be there is an issue with server.

RE: Integration fails when token expires

Nupoor Gupta — Tue, 09 Jan 2024 08:38:21 GMT

When POST method is used, then it is giving 500 error and when changed to GET, then 401, maybe we need to connect with the API team to resolve

RE: Integration fails when token expires

Stefan Helzle — Tue, 09 Jan 2024 08:35:44 GMT

What kind of API is that?

When there is an issue with authorization, it should return a 401, but not a 500.

I suggest to get in contact with the API development team to discuss this issue.