Options
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Greetings 😁
For about a month or two now I have been having issues with some integrations that gets their token invalidated mid-run for no apparent reason.
For example this is from a run yesterday posting to JournalTransactionV2, failing at post 530 of 550, and all remaining attempts fail.
Response:
{
"statusCode": 401,
"headers": {
"Strict-Transport-Security": "max-age=31536000; includeSubDomains",
"ipp-request-id": "f886bdd5-9833-4259-a81f-e1d28c516659",
"Transfer-Encoding": "chunked",
"Date": "Mon, 13 Jun 2022 15:17:42 GMT",
"Server": "Apache/2.4.25,(Debian)",
"Content-Type": "application/json",
"Content-Length": "184"
},
"body": {
"ExceptionType": "IPPException",
"ExceptionMessage": "Invalid Token",
"ExceptionFaultCode": "12010",
"ExceptionMessageID": "12010_04b903ba-5dc2-41f5-b21e-b20ab1d5ec3b",
"ExceptionDetails": ""
}
}
I realize I could rewrite all the integrations to ask for a new token if this happens, but I feel like the token system should not be this fragile. There may be a deeper issue that should be resolved, or it may be all my fault for some unknown reason 😁
Solved! Go to Solution.
4 REPLIES 4
Hi,
- How often do you receive invalid token error ?
- Are you renewing it after the error and using the new one ?
- Do you have another integration/s using the same API Client ID and the same Visma.net Financials ERP User ? (Token-Authentication)
ℹ️ Each consecutively generated token automatically invalidates the recently created one.
(If the request made from the Same CLIENT ID & the Same Visma.Net Financials user for all integrations/company)
Then it probably is caused by a test run I triggered requesting a new token!
Thank you for the clarification of invalidation 🙂