I'm looking in a way to set an expiration date for my authentication token on my pcloud remote. Currently, rclone set the token to have no expiration date. I didn't find on the documentation a way to set it during the remote config. Only a way to change the token manually, which is from an oauth2 connection.
I've tried to just change manually in the config the expiration date, however it doesn't change the fact the bearer token I have has an unlimited expiration date
Run the command 'rclone version' and share the full output of the command.
rclone v1.65.2
- os/version: Microsoft Windows 10 Pro 22H2 (64 bit)
- os/kernel: 10.0.19045.4046 (x86_64)
- os/type: windows
- os/arch: amd64
- go/version: go1.21.6
- go/linking: static
- go/tags: cmount
Which cloud storage system are you using? (eg Google Drive)
Yes, I thought the functionnality was up since it was mentionned in this documentation and in the config file there's a field for an expiration date (but set to 0001-01-01...). I've thought it was dangerous to let a token existing with full rights without an expiration and tried to look any solution to change that.
Thx for the answer, I'll make the issue
i agree 100%
i work mostly with s3 remotes, which in a way are worse than pcloud, no token, so in effect without expiration.
i have to work around that using temporary sessions tokens that always expire.
there are many users in for forum more experience with oauth tokens.
maybe you can craft your own token as a JSON blob.
or maybe, if you program in go, should be easy to add the field expire_inactive.
else, as a kludge, use a proxy between rclone and pcloud api server, add that field.