Masthead username toggle does not uses fullName

[ShaharIlany]

Just updated to 4.15.0-0.okd-2024-03-10-010116

The text at the top left corner of the console used to be my full name, now it just displays my username (my email) instead.

Is this intended behavior?

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[spadgett]

Hi, is this is an intentional change. We can't always rely on having access to the user's full name with external OIDC providers, so we've changed the masthead to show the user's email address. Please let us know if this causes an issue.

/close

[openshift-ci]

@spadgett: You can't close an active issue/PR unless you authored it or you are a collaborator.

In response to this:

Hi, is this is an intentional change. We can't always rely on having access to the user's full name with external OIDC providers, so we've changed the masthead to show the user's email address. Please let us know if this causes an issue.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[ShaharIlany]

It can be nice to have the ability to choose what field will be shown there.
As an alternative, email can be shown as a fallback only if the full name is undefined/null

I work at a company where most of the user's emails are just meanless numbers and letters before the domain part, which says nothing to the user.

@spadgett

[spadgett]

Let me reopen the issue, and we'll consider adding it back. Thanks for the feedback!

@jhadvig @alimobrem FYI

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[logonoff]

/remove-lifecycle rotten
/reopen

Still an issue

[openshift-ci]

@logonoff: Reopened this issue.

In response to this:

/remove-lifecycle rotten
/reopen

Still an issue

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[logonoff]

/lifecycle frozen