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
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
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.
The text was updated successfully, but these errors were encountered: