Deep-linking with reverse proxy auth

[DennisGlindhart]

What would you like to be added?

Ability to deep-link, like needed in issue #5340, but when using Reverse Proxy using Authorization header auth (i.e. oauth2 proxy - described here https://github.com/kubernetes/dashboard/blob/master/docs/user/access-control/README.md#authorization-header).

In that case the user/browser does not hit the login-page (which saves the destination / History.pushState() ). Since the "deep-link" part is in the hast-part of the url, it is never being sent to the backend/reverse proxy, so it is not able to save or track that and redirect back once user is logged in.

Why is this needed?

Same as #5340 - Not having to manually navigate to the deep-linked resource if user was not already logged in.

[floreks]

I am not sure how we could save the state on our side if the proxy redirects to the OIDC login page first without ever hitting Dashboard. The proxy should take care of that and return to the last accessed URL after successful login.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale