-
Bug
-
Resolution: Fixed
-
Low
-
3.1.0
-
Severity 3 - Minor
-
-
RtB - Service ops & Tech entropy
Issue Summary
This is reproducible on Data Center: yes
Steps to Reproduce
- Enable trace logging
- Call any method in
com.atlassian.bitbucket.user.SecurityService
which takes in a `reason` param, and then use the returned
EscalatedSecurityContext, e.g. :securityService.withPermission(REPO_READ, "Reading something") .call(() -> { apply(); return null; });
Expected Results
The `reason` param is logged, as per the javadoc
@param reason a description of the reason for creating the custom security context. This description is used for logging.
Actual Results
The `reason` param is not logged
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available