The transaction ID used in access events for CREST endpoints is not the same as the one used for transaction ID propagation.
- Enable transaction ID propagation in DS
- Call any AM CREST endpoint which results in a call to DS
- Locate the relevant audit events in the logs for AM and DS
AuditEventFactory.accessEvent sets the event's transaction ID from AM's AuditRequestContext (thread local). However, the subsequent call to AccessAuditEventBuilder.forHttpRequest results in this value being overwritten:
The same issues affects the other methods of CrestAuditor.