Invalid CSRF token error during authentication: OAuth2 Proxy update needed

[timurkhis]

Describe the bug

Che operator depends on deprecated version of oauth2-proxy which causes SSO issues with csrf token.

Here is a well known third-party bug coming from oauth2-proxy 7.2.0 (currently used by che-operator):
oauth2-proxy/oauth2-proxy#817

The fix is merged and included in version 7.4.0:
oauth2-proxy/oauth2-proxy#1708

Could you please upgrade the oauth2-proxy dependency version?

Original issue:

1. Configure the Che instance to use and SSO authentication service (for example Okta);
2. Open one tab to the Che address and wait for the login form to appear;
3. Open a second tab to the same Che;
4. Log in in one of the tabs;

Expected result: the login process is successful
Actual result: unhandled error is returned: Login Failed: Unable to find a valid CSRF token. Please try again

Che version

7.57@latest

Steps to reproduce

1. Configure the Che instance to use and SSO authentication service (for example Okta);
2. Open one tab to the Che address and wait for the login form to appear;
3. Open a second tab to the same Che;
4. Log in in one of the tabs;

Expected result: the login process is successful
Actual result: unhandled error is returned: Login Failed: Unable to find a valid CSRF token. Please try again

Expected behavior

Login success

Runtime

other (please specify in additional context)

Screenshots

No response

Installation method

chectl/latest

Environment

Linux

Eclipse Che Logs

No response

Additional context

microk8s

[tolusha]

@timurkhis
Pls, have a look eclipse-che/che-operator#1574