CLARISA (CGIAR Level Agricultural Results Interoperable System Architecture) Is a platform that helps to transform raw data on CGIAR research and activities into meaningful information
0
stars
0
forks
source link
Token refresh interception not working properly #37
With the implementation of the refresh token, an HttpInterceptor was created to check the Access Token (AT) expiration for every outgoing request. If it is expired, an exception is thrown from the back-end. After this, the exception is being handled by requiring the back-end service to update the AT, by using the Refresh Token (RT).
Somehow this "exception handling" is getting skipped once, as an error is appearing in the browser's console, but after, the request to refresh the AT is being made correctly.
We need to check why is this happening. The issue does not break any functionality but is cluttering the console with useless messages.
Acceptance Criteria
[ ] Identify what is exactly the problem
[ ] Solving the problem, leaving the console without the "401 Unauthorized" errors.
Description:
With the implementation of the refresh token, an HttpInterceptor was created to check the Access Token (AT) expiration for every outgoing request. If it is expired, an exception is thrown from the back-end. After this, the exception is being handled by requiring the back-end service to update the AT, by using the Refresh Token (RT).
Somehow this "exception handling" is getting skipped once, as an error is appearing in the browser's console, but after, the request to refresh the AT is being made correctly.
We need to check why is this happening. The issue does not break any functionality but is cluttering the console with useless messages.
Acceptance Criteria
Evidences