Red Hat Bugzilla – Bug 1092213
AccessAuditContext domainUUID is not set when the domain-uuid header is set
Last modified: 2014-08-11 22:08:39 EDT
Description of problem: org.jboss.as.domain.controller.operations.coordination.PrepareStepHandler creates a UUID and sets "operations-headers" => "domain-uuid" on the op, but it does not pass the same UUID to AccessAuditContext. The result is the log record has null in the domainUUID field but the operation headers part of the "ops" field shows the uuid. Confusing. How reproducible: Always. Steps to Reproduce: 1. Start a managed domain 2. Turn on management audit logging. 3. Invoke an operation and check the audit log Actual results: The domainUUID field in the audit log record has no value but the op field that shows the operation that was invoked includes a domain-uuid operation header. Expected results: The domainUUID field in the audit log record has a value but there is no domain-uuid operation header. Additional info:
Refactored release note text for this as a Known Issue (ER4 fixes will not be picked up in the 6.3.0 Beta release) Original note included here for use at 6.3.0 GA: Cause: PrepareStepHandler creates a UUID and sets "operations-headers" => "domain-uuid" on the op, but it does not pass the same UUID to AccessAuditContext. Consequence: In a managed domain operation for an operation on the domain controller, the domainUUID field in the audit log record has no value but the op field that shows the operation that was invoked includes a domain-uuid operation header. Fix: PrepareStepHandler passes the UUID to AccessAuditContext making it available for use in the audit log, while the OperationContextImpl caches a copy of the operation prior to any modifications ensuring that headers added for internal reasons during execution are not recorded in the log. Result: The domainUUID field in the audit log record has a value but there is no domain-uuid operation header.
Verified on EAP 6.3.0.ER4