-
Notifications
You must be signed in to change notification settings - Fork 4
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
Sonarr V4: Passwords and API keys are obfuscated #34
Comments
Upstream has decided on not providing a way to detect if a password was actually changed or not, but ensuring that notification connections, and other resources, are not re-tested if no parameters have changed. This is not ideal, but I can rework the password handling to hopefully reduce the impact of this. |
I had a related issue but I figured out it wasn't what I thought it was. Seems prowlarr is doing the same thing, so seems when you refetch to validate you get the '****' and it fails validation. I can open a separate ticket if you'd like but these all seem like same general issue.
|
Hi @jvrobert, thanks for reporting the issue, and sorry for the late reply. I have had another user report the same thing regarding Prowlarr. I will make a new release of the Prowlarr plugin to resolve the issue in the interim, while I come up with a more permanent solution for handling this. |
Hi @jvrobert, I have released a fix for this issue in the following packages:
Please let me know if this resolves your problem. |
#34
Sonarr V4 introduced a change where any passwords or API keys returned via the API (and to the UI) are obfuscated with
*
characters.This makes it impossible to idempotently check and update resources with API keys or passwords in them.
I have created an issue upstream, to see if a solution to this issue can be reached.
Upstream issue: Sonarr/Sonarr#6169
The text was updated successfully, but these errors were encountered: