Transmission fields for Auth don't need to be 'required'

[Hybes]

Environment

Docker

Version

0.14.0

Describe the problem

Instead of being nasty, we could understand how the credentials for Transmission integration are not needed and remove the required field on these inputs.

Logs

No response

Context

No response

Please tick the boxes

• [X] I confirm that I attached the proper logs
• [X] I've read the docs
• [X] I've checked for duplicate issues
• [X] I've tried to debug myself

[Hybes]

in reference to #1594 , which is now closed due to pettiness, the required input field is the issue, and if you 'simply' remove the required prop from the inputs, you can indeed save the configuration. the solution should be to remove the prop from the input on the Transmission Integration, or have the 'clear' button that was mentioned implemented, so we could remove the non-required inputs.

[Meierschlumpf]

In my opinion you should not host your Transmission without auth, but thats just personal opinion

[Hybes]

it's in a local environment and there is no configuration in the image im using to set it up, it doesn't mean the solution is being irrational to people on GitHub...

[SeDemal]

It is recommended to add credential to your apps, especially one that has access to data. Being a close network is not as safe as you think. This is the reason why we require a login, as an incentive for users to have better safety practices. That being said, if you really don't want to add a login, just type some word that you can easily search for, save, then go edit the config in a text editor and just remove the word in question, leaving just the ""

[ajnart]

You can just put in random credentials and it will work. I closed your issue previously because you didn’t even try to look for an answer We are using generative code to create the integrations field on the fly with their types, it would require a lot of work in order to make these fields not required just for your use case and required in others. We’ve had people open issues and fix it themselves by playing around and figuring out that they can use any user/pass or by reinforcing security by adding an authentication method. We do not want to pander to every kind of installation, there are recommendations and if you are not following them then you are outside of the use scope of homarr and you should either find a way around it or get over it.

I do agree that this caveat is not documented well enough, it could be documented in the “transmission integration” part of the documentation website, that way our support bot would have an easier time finding knowledge about it

[github-actions[bot]]

Hello 👋, this issue has been open for 60 without activity. Please close this issue if it's no longer relevant or has been resolved. Still relevant? Simply reply and I'll mark it as active.