-
Notifications
You must be signed in to change notification settings - Fork 693
Closed
Bug
Copy link
Labels
affects/8.8Issue is affecting 8.8 minor versionsIssue is affecting 8.8 minor versionscomponent/identityRelated to the Identity component/teamRelated to the Identity component/teamkind/bugCategorizes an issue or PR as a bugCategorizes an issue or PR as a buglikelihood/midObserved occasionallyObserved occasionallyseverity/criticalMarks a stop-the-world bug, with a high impact and no existing workaroundMarks a stop-the-world bug, with a high impact and no existing workaroundversion:8.8.0-alpha8version:8.8.0-alpha8-rc1version:8.8.0-alpha8-rc2version:dryrun-8.8.0-alpha6-rc999
Description
Description
When an exception is raised during the processing of a record, the entire record is printed to the log, comprising of the authorization
field
Steps to reproduce
- Make a processor return an exception (for example by exceeding the maximum size)
- The entire
authorization
object is printed in the logs
Current behavior
When an exception is raised during the processing of a record, the entire record is printed to the log, comprising of the authorization
field
Expected behavior
the authorization
object should not be printed to the logs as it contains sensitive informations (the user token)
Environment
SM
Version
- Component Version: [e.g. 2.0.0]
Rootcause
No response
Solution ideas
No response
Dev -> QA handover
Links
Log example
``` Expected to process record 'TypedRecordImpl{metadata=RecordMetadata{recordType=COMMAND, valueType=JOB, intent=COMPLETE, authorization=AuthInfo{TOKEN IN PLAIN TEXT}, value={"deadline":-1,"timeout":-1,"worker":"","retries":-1,"retryBackoff":0,"recurringTime":-1,"type":"","customHeaders":[packed value (length=1)],"variables":"gqlpbmNpZGVudHOa3gAZqXJlZmVyZW5jZahJTkMtMzExMqRuYW1l2SVTVVBQT1JULTI4MTkzIC0gSGl0IGVudGVyIFRvbyBRdWlja2x5sGR1cmF0aW9uX21ldHJpY3OSga9kdXJhdGlvbl9tZXRyaWOComlkujAxR0daNTcxRkdQMkY5RDNFVFdWSjFBUEtRpG5hbWWxSW5jaWRlbnQgZHVyYXRpb26Br2R1cmF0aW9uX21ldHJpY4KiaWS6MDFKSDJFUVpQM0I3VkMwREVBOU43Q0pIQkukbmFtZbNUaW1lIHRvIGludmVzdGlnYXRluWluY2lkZW50X3JvbGVfYXNzaWdubWVudHOUgqRyb2xlialzaG9ydGZvcm2pY29tbWFuZGVypG5hbWWySW5jaWRlbnQgQ29tbWFuZGVyq2Rlc2NyaXB0aW9u2gEXVGhlIEluY2lkZW50IENvbW1hbmRlciAoSUMpIGxlYWRzIGFuZCBjb29yZGluYXRlcyB0aGUgZW50aXJlIGluY2lkZW50IHJlc3BvbnNlIC0gbWFraW5nIGtleSBkZWNpc2lvbnMsIG1hbmFnaW5nIGNvbW11bmljYXRpb24sIGVuc3VyaW5nIGRvY3VtZW50YXRpb24sIGFuZCBjYW4gZXNjYWxhdGUgcm9sZXMgYXMgbmVlZGVkOyBmb3IgbWUgcmVhZCAnVGhlIDEyIGtleSBleHBlY3RhdGlvbnMgYW5kIGFjdGlvbnMgd2hlbiB3b3JraW5nIG9uIGFuIGluY2lkZW50JyBpbiBvdXIgaGFuZGJvb2suomlkujAxRzFGV1IwUkdTVzkzR0ZFNVBER1ZUMjFGqXJvbGVfdHlwZa...}' without errors, but exception occurred with message 'Can't append entry: 'RecordBatchEntry[recordMetadata=RecordMetadata{recordType=COMMAND, valueType=PROCESS_INSTANCE, intent=COMPLETE_ELEMENT, authorization=AuthInfo{format=UNKNOWN, authData=, claims={}}}, key=2251799814038713, sourceIndex=-1, unifiedRecordValue={"bpmnElementType":"SERVICE_TASK","elementId":"Activity_0sworoe","bpmnProcessId":"Process_12xghqu","version":5,"processDefinitionKey":2251799814038389,"processInstanceKey":2251799814038603,"flowScopeKey":2251799814038603,"bpmnEventType":"UNSPECIFIED","parentProcessInstanceKey":2251799814038581,"parentElementInstanceKey":2251799814038600,"te… [message truncated due to size]</detail>
</details>
Metadata
Metadata
Assignees
Labels
affects/8.8Issue is affecting 8.8 minor versionsIssue is affecting 8.8 minor versionscomponent/identityRelated to the Identity component/teamRelated to the Identity component/teamkind/bugCategorizes an issue or PR as a bugCategorizes an issue or PR as a buglikelihood/midObserved occasionallyObserved occasionallyseverity/criticalMarks a stop-the-world bug, with a high impact and no existing workaroundMarks a stop-the-world bug, with a high impact and no existing workaroundversion:8.8.0-alpha8version:8.8.0-alpha8-rc1version:8.8.0-alpha8-rc2version:dryrun-8.8.0-alpha6-rc999
Type
Projects
Status
Done