DJAngel973 · DJAngel973 · Jul 2, 2026 · Jul 2, 2026 · Jul 2, 2026 · Jul 2, 2026
diff --git a/README.md b/README.md
@@ -225,6 +225,20 @@ src/
 
 No credentials are stored in the repository — `.env` is gitignored and `.env.example` serves as a template.
 
+### Why sessions instead of JWT?
+
+This project uses **session-based authentication** because it is a **server-rendered application** built with **Thymeleaf**.
+
+| Factor | Sessions (this project) | JWT |
+|---|---|---|
+| Frontend | Thymeleaf (SSR) | React, Angular, Vue, mobile apps |
+| State location | Server (memory/Redis) | Client (the token itself) |
+| Best for | Dashboards, internal portals, admin panels | Mobile apps, microservices, public APIs |
+| Complexity | Low — Spring Security handles it out of the box | Higher — token storage, refresh, rotation |
+| Revocation | Instant — delete the session on the server | Delayed — token remains valid until it expires |
+
+In a real-world scenario, this application would serve a single company's HR dashboard where recruiters (ADMIN) and candidates (USER) log in from their own devices — each with their own independent session. Sessions are the correct tool for this stack and use case.
+
 ## CI/CD — GitHub Actions
 
 This project uses **GitHub Actions** for continuous integration. The pipeline is defined in `.github/workflows/ci.yml` and runs automatically on every push and pull request to `main`.

diff --git a/images/List_Questionnaries.png b/images/List_Questionnaries.png
diff --git a/images/Login.png b/images/Login.png
diff --git a/images/Quiz.png b/images/Quiz.png
diff --git a/images/Registro.png b/images/Registro.png
diff --git a/images/Result.png b/images/Result.png
diff --git a/images/Successful.png b/images/Successful.png