Use Internext otp secret instead of totp code

Feature
1

[I already have this implemented, pushing PR soon]

Hi all,

I have been using Internext for quite sometime to backup my NAS, and using it with restic is great. The Internext integration have a great reliability issue. Using TOTP instead of 2FA Seed code. (The reality of it, it should use another OAuth2.0 flow than client credentails, but that's not the point).

To increase the reliability, instead of giving rcloen the 2fa code, we should give it the 2fa secret (which is used to generate the code). This will make sure that rclone can re-authenticate if something goes wrong. Which makes the integration more robust and reliable.

I have the implementation ready. will push the PR soon.

Thank you all.

Adel

2

One thing I would like to see in the PR/docs is a clear warning that the TOTP secret becomes equivalent to a reusable second factor. For unattended backups that may be the right tradeoff, but then the rclone config really needs to be protected/encrypted and backed up carefully. Otherwise people may think it is just like entering one temporary 6-digit code.