at the 2020 March 11 Technical Committee meeting, we were discussing invalid token issues spotted both in core and Malawi implementation.
It shows up as endpoint calls response with an error message which indicates an invalid token as a cause.
The bug appears under huge workload i.e. performance tests or Malawi instance normal usage. At Malawi, the update of orderables increased the occurrence of this error. We are currently investigating it and for now, we know that:
- this is a service level authorization token,
- the token itself is valid.
We have increased the logging level for the Spring OAuth but it didn’t show any useful information.
Our next steps are:
- increasing the logging level for the Spring OAuth for Malawi,
- try to increase the pool size of the JDBC connection (link).
Most likely it is not related to token expiration. What do you think might be the root cause of the issue?