Skip to content


session id and security concerns #173

fandrei opened this Issue · 3 comments

3 participants


Currently the latency recorder uses CIAPI session id to identify AppMetrics reporting session as well. The problem is that CIAPI session id is sensitive information and potentially can be sniffed.
What about using something else instead?


PS I'd prefer to make it configurable, the same as ApiClient.AppKey

@mrdavidlaing mrdavidlaing was assigned

session id removed from metrics reporting. alternate identifier TBD

@bitpusher bitpusher closed this
@fandrei fandrei reopened this

My suggestion: add MetricsSession property and initialize it from constructor parameter, the same way as AppKey

@bitpusher bitpusher was assigned
@bitpusher bitpusher closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.