New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Onedrive token revoked within 90 days #4512
Comments
What do you think should be done if rclone is not using the remote for more than 90 days? |
You don't have to do that. Just run
|
I think it should be a document modification. Not many users know this thing. They think rclone should renew the token when they use it next time. maybe we need a hint about how to setup a schedule task to avoid the expiry of Onedrive tokens. |
Where is that documented? I don't see this for either my onedrive personal or onedrive business account? Every time rclone does a token refresh it should get a new refresh token. If you don't use the backend at all for 90 days it might expire I suppose - is that what you are seeing? |
Just search “Refresh Token Max Inactive Time” It is not part of onedrive but active directory. |
I'm not sure what to suggest other than adding some stuff to the docs? If you don't run rclone for 90 days then yes, the refresh token will time out. However nearly all the cloud providers are like that. |
I think a suggestion in the docs and the view of adding a new Onedrive account is enough? |
It is counterintuitive that a refresh token is not immortal. |
OK I've put a note in the docs about this and how to refresh the token. Thanks for bringing this up. |
I have met a thread in the forum about onedrive token revoking.
https://forum.rclone.org/t/onedrive-token-keeps-getting-revoked/15479/9
The refresh token of onedrive dies in about 90 days. So if someone do not use an onedrive token for more than 90 days, he may get an error of invalid_grant.
It is very annoying to delete this account and reauthorize it in rclone.
Maybe we should add some way to refresh all of the onedrive tokens regularly.
The text was updated successfully, but these errors were encountered: