azureadv2 won't request a client_id token
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.6k
- Forks
- 631
- PR merge metrics
- No merged PRs in 30d
Description
I used example.go as a base, the program authenticates, but after that it doesn't save a session, I think it doesn't make a request to the token endpoint.
What happens is I only get to see the user info (see the HTML template below) if I render the page from withing the /signin handler. If I get out of that page or redirect, the data is lost and I get an error that says the session couldn't be found.
Contributor guide
No contributing guide indexed for this repository
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 with example.go and the /signin handler, reproducing the AzureADv2 flow through the redirect. Trace whether the token endpoint request and session persistence occur after authentication, using the reported session-not-found error as the checkpoint. Done means the client_id token request is made and user information remains available after leaving /signin.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, go
- Domain
- authentication, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100