-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
[$250] Always mask auth tokens when exporting Onyx state #47995
Comments
cc @mountiny |
Current assignee @mountiny is eligible for the AutoAssignerNewDotQuality assigner, not assigning anyone new. |
📣 @kyy23! 📣
|
Hello, TMisiukiewicz |
Merged! |
@muttmuure it appears that we haven't processed payment for this issue. Can you double check it? Thank you |
Job added to Upwork: https://www.upwork.com/jobs/~021838166767638673695 |
Current assignee @hoangzinh is eligible for the External assigner, not assigning anyone new. |
Invited |
@muttmuure I haven't received the Upwork offer yet. Can you check it again? Thank you |
Can you share your upwork profile? |
Sent you in Slack @muttmuure |
Offer sent |
Accepted. Thanks @muttmuure |
cc @muttmuure for payment so we can close this issue ^ |
Paid! |
Problem
When exporting the Onyx state from the Troubleshoot section, sensitive information such as
authToken
andencryptedAuthToken
are not masked by default. These tokens remain exposed until the "Mask fragile user data" option is explicitly enabled. This could lead to a security vulnerability, as anyone with access to the exported state file could potentially view or misuse these tokens.Solution
To mitigate this risk, it should automatically mask
authToken
andencryptedAuthToken
regardless of whether the "Mask fragile user data" option is enabled.Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @Issue Owner
Current Issue Owner: @muttmuureThe text was updated successfully, but these errors were encountered: