fix(admin-ui): large header issue

[moabu]

Describe the bug

Looks like this is caused when a client has too many scopes stuffed in the jwt in the Authorization header, which causes the request header fields too large error

[duttarnab]

Can the team please share the authorization header? I will check the scopes added.

We will make changes in admin-ui so that instead of adding all scopes to the auth token ... we will add scopes based on the requested config-api endpoint.

[nynymike]

Please expedite this fix for the next release of Flex.

[duttarnab]

sure, we are working on this.

[duttarnab]

Backend changes Update: (JanssenProject/jans#6413)

We have drafted a PR. The /api-protection-token has been modified. We have added a parameter called permissionTag (an array) to the request body. The endpoint will only add permissions (scopes) to the config-api token whose tags are included in the permissionTag parameter. This will help in including only the permissions in the token that are required for making a request. Hence, it will reduce the length of the token.

Forntend changes required:

The front-end (FE) will retrieve tags from a request-tag mapping configuration file and include them in the permissionTag parameter when making the request.

cc: @jv18creator

[jv18creator]

Admin UI will check for individual access token with tag, based on it, FE will call /api-protection-token which will generate access_token for specific permission. If there's already an access_token for that permission then we'll reuse that access token from redux store.