WIP: Add account authentication support to web app #41

Draft
luca0N wants to merge 1 commit from dev_client_auth into dev
Owner

Add account authentication support to the web app. This pull request does not include account support in the backend server.

  • Add login page prototype
    • Add option to stay logged in
    • Make login page functional
  • Add "Forgot password?" page prototype
    • Make "Forgot password?" page functional
  • Check for server authentication support/requirement in main page1
  • Store session token/ID (to be decided) with either cookies or localStorage

  1. Account authentication is optional. Instance administrators can either require it, or leave it disabled. The web app should check whether the server it's configured to use requires authentication before redirecting the user to the relevant page. ↩︎

Add account authentication support to the web app. This pull request does not include account support in the backend server. - [x] Add login page prototype - [ ] Add option to stay logged in - [ ] Make login page functional - [ ] Add "Forgot password?" page prototype - [ ] Make "Forgot password?" page functional - [ ] Check for server authentication support/requirement in main page[^1] - [ ] Store session token/ID (to be decided) with either cookies or localStorage [^1]: Account authentication is optional. Instance administrators can either require it, or leave it disabled. The web app should check whether the server it's configured to use requires authentication before redirecting the user to the relevant page.
luca0N self-assigned this 2026-02-01 18:28:11 +00:00
In the web app, create a new page for authentication, and add a new
route for it.  The page included is only a prototype which does not yet
include the authentication code.
Author
Owner

Note that support for accounts is not yet implemented in the server. This will be worked on in another pull request. I am still deciding how authentication will be implemented (either a simple session token with cookies/bearer authorization, or JWT).

Note that support for accounts is not yet implemented in the server. This will be worked on in another pull request. I am still deciding how authentication will be implemented (either a simple session token with cookies/bearer authorization, or JWT).
This pull request is marked as a work in progress.
This branch is out-of-date with the base branch
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin dev_client_auth:dev_client_auth
git switch dev_client_auth

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch dev
git merge --no-ff dev_client_auth
git switch dev_client_auth
git rebase dev
git switch dev
git merge --ff-only dev_client_auth
git switch dev_client_auth
git rebase dev
git switch dev
git merge --no-ff dev_client_auth
git switch dev
git merge --squash dev_client_auth
git switch dev
git merge --ff-only dev_client_auth
git switch dev
git merge dev_client_auth
git push origin dev
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks
Reference
luca0N/lanbassador!41
No description provided.