8000 When we publish workbooks or datasources and use debug mode, user and password are displayed in plain text · Issue #1024 · tableau/server-client-python · GitHub
[go: up one dir, main page]

Skip to content

When we publish workbooks or datasources and use debug mode, user and password are displayed in plain text #1024

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

Closed
DieKry opened this issue Apr 12, 2022 · 1 comment · Fixed by #1035
Assignees

Comments

@DieKry
Copy link
DieKry commented Apr 12, 2022

extract_from_log_publishing_using_debug_mode.txt
Our environment:
Tableau ServerVersion: 2021.4.2 (20214.21.1217.2252) 64-bit LINUX
TableauServerClient: 0.17.0
Python: 3.8

The excerpts from the log show this fact. It is not relevant whether we publish workbooks with embedded datasources or with published datasouces. Can the output of user and password in the LOG be suppressed or encrypted when we use debug mode? We actually expect this to be the case.
In the excerpts user, password, database server and port were replaced.
I added the excerpts from the log in the attached file.

@jacalata. Sorry for the delay, but I had a few days vacation. In the meantime I was able to install version 0.19.0 in a test environment and verify that no sensitive data is visible in plain text. Thanks a lot, works as expected.

@jacalata jacalata added the bug label Apr 13, 2022
@jacalata jacalata self-assigned this Apr 13, 2022
@jacalata jacalata linked a pull request May 8, 2022 that will close this issue
@jacalata jacalata added the in-progress Issues that are in-progress of being fixed label May 15, 2022
@jacalata jacalata added fixed and removed in-progress Issues that are in-progress of being fixed labels Jun 7, 2022
@jacalata
Copy link
Contributor
jacalata commented Jun 7, 2022

@DieKry this fix is now available in the latest release, 0.19.0. Please let us know if you continue to see any sensitive values logged after updating!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants
0