From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id C9B151FF13C for ; Thu, 16 Apr 2026 15:47:29 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 9AC997002; Thu, 16 Apr 2026 15:47:29 +0200 (CEST) From: =?UTF-8?q?Fabian=20Gr=C3=BCnbichler?= To: pbs-devel@lists.proxmox.com, Arthur Bied-Charreton Subject: applied: [PATCH proxmox-backup v2] fix #7337: Keep track of deep link on OpenID login Date: Thu, 16 Apr 2026 15:46:40 +0200 Message-ID: <177634719405.669298.13709361583030275453.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260319105507.266484-1-a.bied-charreton@proxmox.com> References: <20260319105507.266484-1-a.bied-charreton@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1776347136657 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.054 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: AAAVUG2KN37FY5RLKJWN35TYEGTOX3Z3 X-Message-ID-Hash: AAAVUG2KN37FY5RLKJWN35TYEGTOX3Z3 X-MailFrom: f.gruenbichler@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox Backup Server development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Thu, 19 Mar 2026 11:55:07 +0100, Arthur Bied-Charreton wrote: > Previously, when opening a deep link without being logged into PBS, the > hash was getting lost, redirecting the user to #pbsDashboard instead of > /#. > > 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. > > [...] Applied, thanks! [1/1] fix #7337: Keep track of deep link on OpenID login commit: 00d70197f8a061e6028080ed407073d594f9798d Best regards, -- Fabian Grünbichler