Try again when CurrentUser request to ANM failed #135
Description
User story
The API-Builder application is using the generated ANM Ssession-Id to obtain information about the user currently logged in. For that, it performs the following request:
/api/rbac/currentuser
Which returns the Login-Name, which is then cached in API-Builder for further requests.
If a customer is using a Load-Balanced Admin-Node-Manager it might happen, that the API-Builder request ends up at the wrong Admin-Node-Manager not knowing this session. Therefore the following error is logged:
{"message":"Error getting current user. Request sent to: 'https://anm.customer.com:443'. Response-Code: 403"}
If session stickyness at the Load-Balancer is properly configured that error should not happen, as the request from API-Builder contains all received headers. Even headers added by the LB.
However, in order to improve the behavior, API-Builder should retry this request at least once to reduce the probability of this problem a bit. Even this will not fully solve the issue, it will hopefully improve it.