[EBT] userId
hash generation
#131144
Labels
Feature:Telemetry
impact:critical
This issue should be addressed immediately due to a critical level of impact on the product.
loe:small
Small Level of Effort
Team:Cloud
Team:Core
Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Team:Security
Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!
v8.2.1
We need to come up with a better logic to generate the hashed
userId
in the telemetry context.Currently, we concatenate the Cloud Deployment ID and the Username and generate a hash out of it. The problem with this approach is that it does not allow us to match this data with Cloud UI users (they do a hash of the Username only). In FullStory, it also splits the session, making it harder to analyze the user funnel from Cloud UI to Kibana and back.
The problem with sending the hash of the
username
only is that users that log in with a different provider to Cloud' SAML might share the same user name (i.e.:elastic
username from the elasticsearch basic authentication method). Using a hash of the username provides a unique count of users that is wrong for this reason.The suggestion is to validate the authentication provider and:
The relevant piece of logic is in the
cloud
plugin:kibana/x-pack/plugins/cloud/public/plugin.tsx
Line 313 in 2f3f919
The text was updated successfully, but these errors were encountered: