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

Edit adapter with user/password fails #3424

Open
dsdbusch opened this issue Jan 14, 2025 · 3 comments
Open

Edit adapter with user/password fails #3424

dsdbusch opened this issue Jan 14, 2025 · 3 comments
Labels
bug Something isn't working

Comments

@dsdbusch
Copy link

Apache StreamPipes version

dev (current development state)

Affected StreamPipes components

UI

What happened?

When you use "Sign (usename & password) in a adapter (here OPC UA adapter) you can store and all is fine. If you EDIT an existing adapter it seems that the ENCYPTED password will be used instead the decrypted password. You will only see the dots, but the length is the same as in the encrypted password shown in the code tab when clicking on adrapter's spyglass.

How to reproduce?

Create an OPCUA adapter using username / password and store. When edit the existing adapter the password will not be accepted any longer - you will have to re-enter the password.

Expected behavior

No response

Additional technical information

No response

Are you willing to submit a PR?

None

@dsdbusch dsdbusch added the bug Something isn't working label Jan 14, 2025
@dominikriemer
Copy link
Member

@dsdbusch we had a similar bug which has been fixed in November, and I can't reproduce the bug with the latest dev version.
Can you please double-check you get this error with the latest development version?

@dominikriemer
Copy link
Member

Hi @dsdbusch could you reproduce the error also with the latest version? Otherwise I would close the issue.

@dsdbusch
Copy link
Author

dsdbusch commented Jan 23, 2025

It seems that on edit the ENCRYPED password will be written inside the password field and internally the "PasswordEncrypted" flag is set to true. Modifying the password in the field will change the "PasswordEncrypted" flag to false - so ALL of the text has to be changed! Also the browser's password manager will notice the password is changed (from clear text to encrypted) - this will fail later if the password manager will use the encrypted password due the flag is wrong. If you know about this, you can handle that. I think the better way will be ALWAYS write the password in clear into the field (it will be displayed like '***********').

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

2 participants