Radarr V5: Passwords and API keys are obfuscated #20
Assignees
Labels
bug
Something isn't working
Comments
This was referenced Nov 12, 2023
Callum027
added a commit
that referenced
this issue
Nov 12, 2023
This adds basic support for Radarr V5, to the point that Buildarr can manage such instances with all currently available configuration parameters. Support for new features have not yet been added. Backwards compatibility with Radarr V4 is retained. * Add the Radarr instance version to the secrets metadata, to allow for version-specific handling * Add support for the `external` authentication method (and maintain compatibility with the `none` authentication method for older versions) * Add support for the `radarr.settings.general.security.authentication_method` configuration field * Loosen the Pushover API key validation requirements in Buildarr, to work around passwords and API keys being obfuscated in Radarr V5 (see #20) Other changes: * Update `radarr-py` to `v0.4.0` * Add the `packaging` library as a dependency for version number comparison
Callum027
added a commit
that referenced
this issue
Apr 26, 2024
Temporary workaround for #20 until a permanent solution for handling obfuscated secret values can be worked out.
This was referenced Apr 26, 2024
Callum027
added a commit
that referenced
this issue
Apr 26, 2024
Temporary workaround for #20 until a permanent solution for handling obfuscated secret values can be worked out.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Radarr V5 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: Radarr/Radarr#9397
The text was updated successfully, but these errors were encountered: