The use of tokenFieldName: id_token when setting usageplan does not result in id_token being used

[ably77]

Describe the bug

When testing oAuth with portal using tokenFieldName: id_token as described in the environment.proto it looks as the though the default access_token is being selected instead of the id_token

To Reproduce** Steps to reproduce the behavior: Create an Environment with UsagePlan and provide the UsagePlan.AuthPolicy.OAuth.tokenFieldName: id_token You can see that the default access_token is still being selected instead of id_token

Expected behavior id_token should be used instead of access_token

Additional context Add any other context about the problem here, e.g.

• Gloo Portal version - 1.1.0
• Kubernetes version - 1.20
• Gateway technology and version (e.g. Gloo Edge Enterprise v1.5.11, Istio 1.7) - Gloo Edge

[chrisgaun]

Update 10/19: Portal team has been able to reproduce this issue but it is not clear why it's not working. Update from Marco that someone with UI experience would need to dig into this, but currently the team is focused on GM work and there is no current plan to pick up this issue in the near-term