OpenListTeam / OpenListTeam/OpenList
[BUG] 阿里云配置好后,refreshtoken失效,需要手动打开保存一次
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 24.7k
- Forks
- 2.3k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 36
Description
Please confirm the following
-
I have read and agree to AGPL-3.0 Section 15 .
The program is provided "as is" without any warranties; you bear all risks of using it. -
I have read and agree to AGPL-3.0 Section 16 .
The copyright holders and distributors are not liable for any damages resulting from the use or inability to use the program. -
I confirm my description is clear, polite, helps developers quickly locate the issue, and complies with community rules.
-
I have read the OpenList documentation.
-
I confirm there are no duplicate issues or discussions.
-
I confirm this is an
OpenListissue, not caused by other reasons (such as network, dependencies, or operation). -
I believe this issue must be handled by
OpenListand not by a third party. -
I confirm this issue is not fixed in the latest version.
OpenList Version (required)
v4.0.8
Storage Driver Used (required)
阿里
Bug Description (required)
每次配置好aliyun后,工作正常,但是一段时间(估计是2小时)后,不能浏览加载的阿里云盘,但是手动打开云盘配置再次保存马上又可以访问,应该是refresh token失效不能自动获取的原因,但是没有找到解决方案。
Configuration File Content (required)
默认配置,没有修改
Logs (optional)
No response
Reproduction Link (optional)
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files, tests, or entry points are named. Start by reproducing the Aliyun storage configuration on OpenList v4.0.8 and observe whether access fails after the reported refresh-token lifetime. Done means the token refreshes automatically without requiring the storage configuration to be opened and saved again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100