Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disabling Data Sanitization in OpenReplay Tracker #1927

Open
Im-HaGGling opened this issue Mar 1, 2024 · 1 comment
Open

Disabling Data Sanitization in OpenReplay Tracker #1927

Im-HaGGling opened this issue Mar 1, 2024 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@Im-HaGGling
Copy link

Describe the issue
I spent approximately 2 hours exploring all potential initialization parameters of @openreplay/tracker to disable "Sanitize Data" in my recordings. Despite following the documentation and turning off all the options I found, the issue persists. Can anyone advise on what I might be doing incorrectly?

Steps to reproduce the issue

  1. Disable all possible sanitizer options during the tracker initialization.
  2. Observe that nothing changes, and the issue with "Sanitize Data" still persists.

Expected behavior
As described in the documentation, I expected that all field data would be plain, meaning filled with real user data instead of being masked with ************.

Screenshots
Not available.

OpenReplay Environment

  • Frontend stack: Next, React, React-DOM
  • OpenReplay version: 1.17
  • Tracker version: 12.0.3.
  • Plugins used: None specified.
  • Cloud provider: Hetzner.
  • System specs: i7 6700k, 64GB RAM, 2xSSD 1TB.

Additional context
Added a code snippet for further clarity on the issue:

const sanitizer = (data: RequestResponseData) => {
  const disallowUrls = ['auth', 'register', 'passwordrecovery']
  if (disallowUrls.some((u) => data.url.includes(u))) {
    data.request.body = null
    data.response.body = null
  }
  return data
}

const domSanitizer = (node: Element) => {
  return SanitizeLevel.Plain
}

const tracker = new Tracker({
  projectKey: process.env.NEXT_PUBLIC_OPENREPLAY_KEY!,
  ingestPoint: process.env.NEXT_PUBLIC_OPENREPLAY_INGEST_POINT!,
  domSanitizer,
  defaultInputMode: 0,
  disableStringDict: false,
  obscureTextEmails: false,
  obscureInputDates: false,
  obscureTextNumbers: false,
  obscureInputEmails: false,
  obscureInputNumbers: false,
  network: {
    sanitizer,
    capturePayload: true,
    failuresOnly: false,
    ignoreHeaders: ['Cookie', 'Set-Cookie', 'Authorization'],
    sessionTokenHeader: false,
    captureInIframes: false,
  }
})

This snippet details the configuration attempts made to adjust sanitization settings within the OpenReplay tracker setup.

@Im-HaGGling Im-HaGGling added the bug Something isn't working label Mar 1, 2024
@estradino estradino assigned nick-delirium and unassigned estradino Mar 1, 2024
@nick-delirium
Copy link
Contributor

would need some example to help me to reproduce the issue and work on it, like what fields are getting masked with those settings vs what aren't

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants