L3 - Default Description
Brief summary of the bug. What is it ? Where is it ?
In case the accounts service cannot be reached by the Optimize backend a call to /api/identity/current/user fails with a 500. This 500 causes the frontend to get stuck with an endless spinner load icon.
Steps to reproduce:
The only thing I can think of now would be starting Optimize in cloud mode locally, while having no connection to accounts.
Actual result :
Expected result:
As based on the user session token we at least have the name of the current user we can fallback and return a response that contains the name set to the userid.
