Timed contains a user that is used by our Customer Center for fetching projects and its details.
According to current implementation, only internal and external users are allowed to fetch project or report details. In order to be an internal or external user, the user needs an active employment, which the mentioned service user didn't have. Although this makes perfect sense, timed rejected requests by the service user which resulted in a broken view in the Customer Center.
Temporary solution:
An employment has been added for the service user.
Suggestion:
Implementation of a new role in timed-backend to allow access to other services such as Customer Center with a standalone user. With this, unnecessary data being stored can be avoided.
c0rydoras
commented
2 months ago
Timed contains a user that is used by our Customer Center for fetching projects and its details.
According to current implementation, only internal and external users are allowed to fetch project or report details. In order to be an internal or external user, the user needs an active employment, which the mentioned service user didn't have. Although this makes perfect sense, timed rejected requests by the service user which resulted in a broken view in the Customer Center.
Temporary solution: An employment has been added for the service user.
Suggestion: Implementation of a new role in timed-backend to allow access to other services such as Customer Center with a standalone user. With this, unnecessary data being stored can be avoided.