In the first iteration, the SWR will primarily show a functionality available to a non-registered user. Nevertheless, we need to prove the authentication and authorisation as well. As such, a lightweight proof-of-concept on functionality available to an authorised user should also be a subject of the first iteration. https://github.com/soilwise-he/Soilwise-userstories/issues/22
[x] primarily functionality available to a non-registered user
[x] a lightweight proof-of-concept demonstrating functionality available to an authorised user
1st iteration use Git(hub) as authorisation, in the 2nd and 3rd iteration will use EU-ID.
With acceptance criteria:
primarily functionality available to a non-registered user
a lightweight proof-of-concept demonstrating functionality available to an authorised user
[x] Basic forms for user registration and login, including validation.
[x] A minimal dashboard page that an authorized user can access after logging in. This will include: Welcome message, Simple user profile information (e.g., username, email)., Basic navigation to additional user-specific features (even if they are placeholders).
[x] Authentication: Implement basic authentication using a secure method (e.g., token-based authentication like JWT or EU login alternative).
[x] Authorization: Ensure that certain routes/pages are accessible only to logged-in users.
[ ] Data Storage: Use a lightweight database (e.g., SQLite) for storing user credentials and profiles.
In the first iteration, the SWR will primarily show a functionality available to a non-registered user. Nevertheless, we need to prove the authentication and authorisation as well. As such, a lightweight proof-of-concept on functionality available to an authorised user should also be a subject of the first iteration. https://github.com/soilwise-he/Soilwise-userstories/issues/22
1st iteration use Git(hub) as authorisation, in the 2nd and 3rd iteration will use EU-ID.
With acceptance criteria:
primarily functionality available to a non-registered user
a lightweight proof-of-concept demonstrating functionality available to an authorised user
[x] Basic forms for user registration and login, including validation.
[x] A minimal dashboard page that an authorized user can access after logging in. This will include: Welcome message, Simple user profile information (e.g., username, email)., Basic navigation to additional user-specific features (even if they are placeholders).
[x] Authentication: Implement basic authentication using a secure method (e.g., token-based authentication like JWT or EU login alternative).
[x] Authorization: Ensure that certain routes/pages are accessible only to logged-in users.
[ ] Data Storage: Use a lightweight database (e.g., SQLite) for storing user credentials and profiles.