microsoft / microsoft/dev-tunnels
When a user is a member of many groups in Entra, they end up with HTTP 431
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 508
- Forks
- 52
- Avg merge
- 20h 6m
- Merged PRs (30d)
- 7
Description
Reopening #435 and #425
Why would you store group memberships in the cookies? If it is because it returns with the token, you can just configure the app registration to omit them - https://learn.microsoft.com/en-us/entra/identity-platform/optional-claims?tabs=appui#configuring-groups-optional-claims
I tried looking through the docs and didn't find any reference to usage of groups anyways. So why not just remove it from the token = solved?
This seems like a fairly simple fix. Any chance anyone can look into it? It is quite annoying issue.
I blogged about this general issue a while ago - https://hajekj.net/2017/10/30/the-dangers-of-too-many-cookies-on-a-website/
/cc: @derekbekoe
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 tracing how Entra group memberships or claims are turned into cookies in the Dev Tunnels SDK. Check the application’s authentication flow and related documentation, then reproduce the many-group case that causes HTTP 431. Done means group membership data no longer makes requests exceed cookie or header limits, with coverage for the affected scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100