Authorization Token expires after 24 hours

[nicklozon]

When a backup takes longer than 24 hours, the initial Authorization Token expires and a new one is required.

[mabeltron]

Just come across this problem running a large backup but the expiry time is now more like 12 hours. There also doesn't seem to be a method of invalidating the existing authorisation token on the client side so once an upload fails that account can't negotiate with Backblaze any more. I'm going to RTFM and see if I can get to the bottom of this.

[nicklozon]

I wrote an updated script, but it never seemed to work quite right. I no longer use duplicity, but I could share it.

[mabeltron]

I started too but decided against using duplicity in the end. The solution would seem to be to take the auth process out of init and invoke it when Backblaze starts to return a 503 error.
I also tried with Hubic, which implements a permanent token on the client - not sure if this would be available to Backblaze.