Hello, we recently received information about upcoming changes to improve security for access tokens related to OAuth 2.0 - first of all, it’s great that you’re doing this.
I checked the current state of keeping access_tokens in our database. Following information in the Changelog it is recommended to increase the size of the column up to 511 characters. Currently length of the oauth token is around 60-ty characters. Even if it will be doubled as mentioned in Changelog it should be max 120 characters.
I would like to understand better why there is a recommendation to increase it up to 511.
Maybe I miss something here, thanks in advance for the help.
If your app has tokens with ~60 characters length, then you are not affected by the upcoming change.
The current change in token length will be applied only to the newer tokens whose length is >200. However, it would be great if you can already reserve more space to meet the recommended minimum, should we increase the security for all remaining tokens in the future, too.
company’s OneDrive account. I usually delete and change file names to correct them. However, this time, I was changing too many GB using OneDrive at the same time as the sync issues are happening at the home folder level and I don’t want to use Disable File On Demand Fetch Lover Content because I have too many GB intentionally not on my computer mine. But since I can only change the file name online (I can’t change file folders on my computer), online (I can’t change file folders on my computer), this may be the only way. I company’s OneDrive account. I usually delete and change file names to correct them. However, this time, I was changing
