Persisting hash fragments on login #2042
TattdCodeMonkey
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Has anyone looked into the ability to persist URL hash fragments on login? This would require some Javascript code to be added to the
/auth
page to check for a hash fragment and then maybe update the state of the AuthRequest.This is an issue when you try to open a route that uses a hash fragment for app routing, like the Kubernetes Dashboard. So you open a URL like:
https://<cluster-url>/dashboard/#/deployment
and are redirected to dex to login:https://<cluster-url>/dex/auth?....#/deployment
that#/deployment
is lost since its only available to the browser. after you login your taken tohttps://<cluster-url>/dashboard/
nothttps://<cluster-url>/dashboard/#/deployment
. You then have to open the original link again to go to the right location, or navigate within the app you're trying to view.Here is an article about solving this issue in general.
Beta Was this translation helpful? Give feedback.
All reactions