From: Arthur Bied-Charreton <a.bied-charreton@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [PATCH] fix #7337: Keep track of deep link on OpenID login
Date: Thu, 12 Mar 2026 15:30:32 +0100 [thread overview]
Message-ID: <20260312143032.409115-1-a.bied-charreton@proxmox.com> (raw)
Previously, when opening a deep link without being logged into PBS, the
hash was getting lost, redirecting the user to #pbsDashboard instead of
/#<deeplink>.
Store `window.location.hash` in sessionStorage (per-tab storage) before
redirecting to the login URL, and add it to the history after successful
login to direct the user to the deeplink they opened.
`#pbsDashboard` remains the default redirect if no deeplink is stored.
Signed-off-by: Arthur Bied-Charreton <a.bied-charreton@proxmox.com>
---
www/LoginView.js | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/www/LoginView.js b/www/LoginView.js
index fd9594f6..b72e4223 100644
--- a/www/LoginView.js
+++ b/www/LoginView.js
@@ -48,6 +48,7 @@ Ext.define('PBS.LoginView', {
if (this.getViewModel().data.openid === true) {
const redirectURL = location.origin;
+ sessionStorage.setItem('openid-deeplink', location.hash);
try {
let resp = await Proxmox.Async.api2({
url: '/api2/extjs/access/openid/auth-url',
@@ -217,7 +218,13 @@ Ext.define('PBS.LoginView', {
let creds = response.result.data;
PBS.Utils.updateLoginData(creds);
PBS.app.changeView('mainview');
- history.replaceState(null, '', `${redirectURL}#pbsDashboard`);
+ let deeplink = sessionStorage.getItem('openid-deeplink');
+ if (deeplink) {
+ sessionStorage.removeItem('openid-deeplink');
+ history.replaceState(null, '', `${redirectURL}${deeplink}`);
+ } else {
+ history.replaceState(null, '', `${redirectURL}#pbsDashboard`);
+ }
},
});
}
--
2.47.3
reply other threads:[~2026-03-12 14:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260312143032.409115-1-a.bied-charreton@proxmox.com \
--to=a.bied-charreton@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox