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

Password not masked in Database connection when datasource added through YAML file. #24321

Closed
MalavikaN1 opened this issue Jun 8, 2023 · 1 comment
Labels
#bug Bug report

Comments

@MalavikaN1
Copy link

MalavikaN1 commented Jun 8, 2023

A clear and concise description of what the bug is.

How to reproduce the bug

  1. Click on setting
  2. Go to Database Connections
  3. Click on edit button in Actions for a dataset

Expected results

The password in the SQLAlchemy URI should be masked with XXXX

Actual results

The password is initially displayed, but once you click on the input box change something and click on finish and then reopen it, it becomes masked.

Screenshots

If applicable, add screenshots to help explain your problem.

Environment

(please complete the following information):

  • browser type and version: Chrome
  • superset version: superset version : latest

2
1

Checklist

Make sure to follow these steps before submitting your issue - thank you!

  • [x ] I have checked the superset logs for python stacktraces and included it here as text if there are any.
  • [x ] I have reproduced the issue with at least the latest released version of superset.
  • [ x] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context

Add any other context about the problem here.

@MalavikaN1 MalavikaN1 added the #bug Bug report label Jun 8, 2023
@rusackas
Copy link
Member

rusackas commented Mar 6, 2024

Hi there, and sorry this has gone quiet for so long. We're no longer supporting Superset 2.x or prior, and it's been a while since this thread saw any activity, so I'm closing this as stale. If it is still an issue in Superset 3.x, we can re-open this, or feel free to open a new issue with updated context.

@rusackas rusackas closed this as completed Mar 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
#bug Bug report
Projects
None yet
Development

No branches or pull requests

2 participants