Thank you very much for this, it is working great for me. One thing that would be great (I may have overlooked it if I did I'm sorry) is allowing this to work with Seafile's two-factor authentication like the CLI can. If this could be added somehow, that would be great. Cheers
I was looking at it over the week-end. I think the best way to do this is probably to login once with user/password/2fa code, then store the authentication token in the configuration. There's no need to keep the user/password.
It can't be done at config time rclone config:
By the time you finish the configuration and connect to a remote, the 2FA code is likely to have expired.
It can't be done via rclone authorize either:
It works at the backend level, not at a remote level (I guess it only works for services with a unique endpoint)
What could be the best approach for this?
Change the way rclone authorize works and allow a remote as a well as a backend?
Create a new rclone 2fa command? (making it generic enough to be re-used by other services if needed)
That's interesting: I was looking at the Config callback but I could only find it called from the authorize command which is not what I wanted. I should investigate it more as it could just be what I need