You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, rqbit lacks built-in support for simple authentication, making it challenging to secure access to the daemon without relying on external tools or reverse proxies. Adding a straightforward username and password authentication mechanism would greatly enhance the usability and security of rqbit for users who need basic access control.
The text was updated successfully, but these errors were encountered:
This might be a bit of an overstatement, at least without TLS :) But agree there is some value in it. Do you propose to wrap the whole API into basic auth, or leave ability to do read-only calls without authentication?
Currently, rqbit lacks built-in support for simple authentication, making it challenging to secure access to the daemon without relying on external tools or reverse proxies. Adding a straightforward username and password authentication mechanism would greatly enhance the usability and security of rqbit for users who need basic access control.
The text was updated successfully, but these errors were encountered: