Feature/ccp 5048 fix email submission link

[bhuvan-aot]

Description

ccp-5048
When an unauthenticated user clicks the "View this submission" link from a submission confirmation email, the app navigates to /form/view?s=.

What was broken:
The FormView route's beforeEnter guard calls getSubmissionStatuses() to check permissions. For unauthenticated users, this returns a 401. The guard was treating 401 the same as 404 — redirecting to the NotFound page. So users saw a 404 instead of being asked to log in.

The fix (router.js):
Split the 401 and 404 handling:

• 401 → call next() with no redirect. Since FormView has requiresAuth: true, the global guard calls authStore.login(), which redirects the user to the Keycloak login page. After login, they land back on the submission view.
• 404 → still redirects to NotFound (submission genuinely doesn't exist).

Type of Change

Checklist

• I have read the CONTRIBUTING doc
• I have checked that unit tests pass locally with my changes
• I have run the npm script lint on the frontend and backend
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)
• I have approval from the product owner for the contribution in this pull request

Further comments

[Copilot]

Pull request overview

Fixes unauthenticated access to the “View this submission” email link (/form/view?s=<submissionId>) so that a 401 from the permission-check call no longer redirects users to NotFound, enabling the intended login/auth flow instead.

Changes:

• Updated the FormView route beforeEnter guard to treat 401 (unauthenticated) differently from 404 (missing submission).
• Preserved NotFound redirect behavior for genuine 404 cases while allowing 401 cases to proceed.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[usingtechnology]

LGTM