You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the session id is logged directly (on debug level).
This allows a malicious user to hijack the session.
We could change the logging of the session id for a trace and/or span id.
We could also look into a distributed tracing mechanism, since multiple services are being called from the same frontend.
The distributed tracing mechanism can show insights on potential bottlenecks and can show an audit log of what a user has done between a specific timespan.
Examples of distributed tracing mechanisms:
Zipkin
Jaeger
Elastic(?)
OpenTelemetry
The text was updated successfully, but these errors were encountered:
Currently the session id is logged directly (on
debug
level).This allows a malicious user to hijack the session.
We could change the logging of the session id for a
trace
and/orspan
id.We could also look into a distributed tracing mechanism, since multiple services are being called from the same frontend.
The distributed tracing mechanism can show insights on potential bottlenecks and can show an audit log of what a user has done between a specific timespan.
Examples of distributed tracing mechanisms:
The text was updated successfully, but these errors were encountered: