Steps to reproduce

1. Make a rest request for a user account that does not exist (e.g. /user/<id>/profile

Observed behavior

• Server log contains the following exception on level warning:

   org.camunda.bpm.engine.rest.exception.InvalidRequestException: User with id [...] does not exist
  	at org.camunda.bpm.engine.rest.sub.identity.impl.UserResourceImpl.getUserProfile(UserResourceImpl.java:56)

Expected behavior

• As this is an expected exception and the error is also communicated via the HTTP status code and error message, it is sufficient to log the exception on a lesser severity level, e.g. FINE

Side notes

• E.g. we could decide the log level based on the http response code, e.g. 5xx is always logged on WARNING, where all other status codes are logged on FINE
• Consider defining a proper logger name and documenting the purpose of this logger
• Make sure to check all exception handlers