Events coming from legacy are not sending userID but only securityToken and HttpInterceptors are not injecting userID.
This can cause problem for developers using context.getUserID without knowing that such case may happen.
Plus, if we send an event within a listener called by the legacy it's context is enriched with userID. This is very confusing.
So, event bus could have the same behaviour than query/command gateway and enrich context with userID directly from the http layer.
Events coming from legacy are not sending userID but only securityToken and HttpInterceptors are not injecting userID. This can cause problem for developers using context.getUserID without knowing that such case may happen.
Plus, if we send an event within a listener called by the legacy it's context is enriched with userID. This is very confusing.
So, event bus could have the same behaviour than query/command gateway and enrich context with userID directly from the http layer.