Description of problem:

Having an user with a high number of groups associated to it (150+) with Aggregated Relations will lead to responses 431 from the API.

This impacts:

• login: during login the response from the API may be 431 making that the client is not able to store the session cookie, breaking auth and making user have to login again;
• user entities: An error will be shown in the UI when opening an user entity that is in this situation

Check the upstream bug and the related RHDHBUGS-20 ticket.

Prerequisites (if any, like setup, operators/versions):

Steps to Reproduce

1. Have an user entity member of multiple groups with Aggregated Relations;

Actual results:

 Error during login and when opening an user entity on software catalog

Expected results:

no errors

Reproducibility (Always/Intermittent/Only Once):

always

Build Details:

Additional info (Such as Logs, Screenshots, etc):

A workaround for this is increase the max header size:

 --max-http-header-size=32768 

Another possible workaround is as stated by Backstage maintainer: "the best fix is probably to significantly reduce the ownership refs count to ensure that the token doesn't grow too large"