Bearer token from application not forwarded by OAuth-proxy

[guimou]

/kind bug

Some applications that can launched as a workbench (example: Langflow) have their own internal authentication mechanism based on a Bearer token.
The current Oauth-proxy configuration does not pass this information (it is stripped from the headers), preventing the application to work properly.
The parameter --pass-user-bearer-token must be added here

What did you expect to happen:
The Bearer token sent from a web app should not be filtered by the Oauth-proxy.

This currently prevents new versions of Langflow to be used as custom workbench images.

[harshad16]

Tasks:

• Write a method to include append --pass-user-bearer-token in the args of the proxyContainer
• Include it only in admission hook:

  kubeflow/components/odh-notebook-controller/controllers/notebook_webhook.go

  Line 235 in 816b1ef

  if req.Operation == admissionv1.Create {

  
  as we don't want old notebook to be hindered.