"client info is null" - WAM broker returns token without client_info (json_parse_failed)
Open
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 1k
- Forks
- 132
- Avg merge
- 5d 19h
- Merged PRs (30d)
- 6
Description
- Version: 0.4.1.19742
- MSAL version: 4.83.1.0 / MsalRuntime 0.20.3
- OS: Windows
10.0.26200, AzureAD joined - Key trace lines: WAM silent auth succeeds → client_info is null on second token acquisition → json_parse_failed
- Repro: workiq logout → delete msal_token_cache.dat → workiq ask -q "test" → first token OK, second call fails
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 reproducing the failure with workiq logout, deleting msal_token_cache.dat, and running workiq ask -q "test" twice; inspect the WAM silent-auth and second-token-acquisition trace. Done means the second token acquisition no longer fails with client_info null or json_parse_failed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- authentication, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100