Hi we have hosted backstage in an enterprise environment and we are using azure ad for authentication. One of the user is getting http request is too big to process error as he is part of 200+ groups/dl which making his request bearer token too large. any solution we can implement to pass this restrictions so even if user is part of too many groups still he can use this platform without any issue.
#HTTP request is too big to process
boreal vault
mild spruce
At this time, all you can do is to modify your sign in resolver code to return a smaller number of groups. Most orgs only actually claim ownership through groups that are properly part of the org structure for example. Like at our place, I am a member of a VERY large number of groups that are only used for administrative reasons like "marking me as having access to third party tool X" or being in some specific email circulation that's implemented as a group. But my ACTUAL OWNERSHIP only stems from me being part of a physical team or two. And those are the only entity refs that the resolver should return for me