Retain URL Fragment (#) After JWT Reauthentication
backlog
V
Vijay Sakthivel
When accessing a knowledge base article using a URL that contains a heading fragment (for example, #section-id), the fragment is not retained if the user is redirected through the JWT reauthentication flow.
After login, the article loads at the top of the page instead of the intended heading, which impacts deep-linking to specific sections. This currently occurs because URL fragments are handled on the client side and are not available during the server-side authentication and redirect flow used for JWT.
Preserving the fragment across reauthentication would provide a more consistent navigation experience for users, even when sessions expire.
Log In
D
D360 Product Management
marked this post as
backlog
Mohamed Shakheen
Hi Lavender Swordfish Vijay
Thank you for sharing the feedback. We’ve reviewed this in detail and wanted to share an update.
This behavior is a known limitation of server-side authentication flows. URL fragments (the part after #) are handled entirely by the browser and are not sent to the server as part of an HTTP request. Since our authentication flow is processed on the server (SSR), the fragment information is not available during login and therefore cannot be preserved after the redirect.
This is standard web behavior and is consistent with how other knowledge base platforms using server-side authentication work as well.
While it’s technically possible to preserve fragments by moving the authentication flow fully to the client side, that would require significant architectural changes and is not something we’re planning at the moment.
That said, we’ll keep this in our backlog and monitor customer traction. Based on demand and impact, we’ll evaluate prioritising this in a future cycle.
V
Vijay Sakthivel
Raised on behalf of Lavender Swordfish