[BUG] With GRPC v1.46.0 non-ascii chars are not permitted in grpc metadata

[pmahindrakar-oss]

Describe the bug

With this change grpc/grpc-go#468

The data populated in metadata has to be ascii data
https://github.com/flyteorg/flyteadmin/blob/6591fa2a6303ee5dc6f47db9c9725cf72c0db99a/auth/handlers.go#L326

Hence umlaut chars used by the User in there IDP provider would fail in admin and throw

Request failed with status code 500 header key "userinfo" contains value with non-printable ASCII characters

Expected behavior

The request shouldn't fail .

Additional context to reproduce

No response

Screenshots

No response

Are you sure this issue hasn't been raised already?

• Yes

Have you read the Code of Conduct?

• Yes

[pmahindrakar-oss]

cc : @katrogan @EngHabu @sbrunk

[bimtauer]

Hi we're using OpenID connect with Google and are having a lot of problems with this since many of our colleagues have non-ascii conforming names 😅 🇫🇮 We solved this now by downgrading flyteadmin, but a quick fix would help us a lot 🙌🏼