and more in a single search tool across platforms. Read the announcement here. |
01/10/2024 07:25 AM - edited 01/10/2024 10:17 AM
Hi Team,
We have Oauth2.0 authentication to generate access_token for Outreach application. When we run the job to import account, we are getting JWT token error. Same token is working from postman.
url-https://<hosturl>/api/v2/Users with Error Message-{"error":"Invalid JWT token.","description":"The JWT token could not be decoded."}
PFA for connectionJSON attached and postman response image.
Any inputs to resolve this issue would be a great help!
Thanks,
Shilpa
01/11/2024 10:10 PM
Hi @Shilpa_B
Could you please generate a new token and try with that. Please ensure there is no space while copying and Bearer is kept before the token.
Also please check the logs and share detailed error snippet/error codes (excluding URLs).
Regards,
Dhruv Sharma
01/12/2024 10:23 AM
01/12/2024 07:03 PM
Hi @Shilpa_B
I can see 400 error code while you get the above-mentioned error. Could you please add 400 in the
"retryFailureStatusCode" and try again. Please use showlogs: true configuration and collect detailed logs.
Regards,
Dhruv Sharma
01/12/2024 08:33 PM - edited 01/12/2024 08:56 PM
Issue is fixed. It was wrong refresh token in connection JSON
03/22/2024 05:56 AM - edited 03/22/2024 05:56 AM
Hi @Dhruv_S
The issue is still not resolved.
The Refresh tokens expire after a time period, and the latest refresh token should be used to regenerate new access and refresh tokens.
I am trying the attached connectionJSON but still getting the error 'responseText:{"error":"Invalid JWT token.","description":"The JWT token could not be decoded."}, cookies:[], statusCode:400]"'
Please assist
Thanks,
Shilpa
03/25/2024 10:28 PM
Hi @Shilpa_B
Please use the attached connection JSON and let us know if it works and share the error message if it doesn't work. 400 error was missing from the retry failure status code and only mentioned in test connection params block. It could be the reason it is unable to retry to fetch latest code.
Regards,
Dhruv Sharma
03/26/2024 03:04 AM
I tried the above json by adding 400 at retryFailureStatusCode. It didn't work. Please find the logs in the attachment.
Note : I have masked the API in the logs
Thanks,
Shilpa
03/26/2024 03:36 AM
Hi @Shilpa_B
As per the logs, I can see that it is trying to get the latest token and trying to attempt till max refresh try count but it is not getting the token and failing the import.
If you validate everything and still face an issue, we will open a FS ticket to look into it.
Regards,
Dhruv Sharma
03/26/2024 10:31 AM
Hi @Dhruv_S,
access_token expires in 2 hours, refresh_token expires in 14 days
Please find my answers inline
Everything is validated but its not working.
Thanks,
Shilpa
03/26/2024 07:51 PM
@Dhruv_S similar issue we are facing https://forums.saviynt.com/t5/identity-governance/rest-connector-token-is-not-re-generated-after-it-...
03/27/2024 01:06 AM
03/27/2024 09:04 PM
we have shared required details
03/28/2024 06:42 AM - edited 04/01/2024 08:51 AM
This seems issue with v23.11
#Edited
Updated ticket for more info