abpframework / abpframework/abp
Write all auth response to the `access-token.bin` in ABP CLI
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 14.4k
- Forks
- 3.7k
- Avg merge
- 15h 32m
- Merged PRs (30d)
- 106
Description
Reason: When the token expires, Suite throws an exception!
1- Write the complete auth response JSON content to the %UserProfile%\.abp\cli\access-token.bin file. (No need because we can decode JWT and get expire date)
2- Check if the token expiration date is still valid for ABP Suite after opening it.
3- Check ABP CLI project creation if the token is still valid.
PS: this is a Preliminary issue of this issue.
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
Start by locating the ABP CLI authentication flow that reads or writes %UserProfile%\.abp\cli\access-token.bin, then trace how ABP Suite opens and how CLI project creation uses the token. Done means the complete auth response is persisted and both Suite startup and project creation reject or refresh an expired token.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- authentication, cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100