ClimApp uses server-side session authentication. When you submit valid credentials toDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/elenacarino-max/mas-climapp/llms.txt
Use this file to discover all available pages before exploring further.
POST /login, the server stores your email in the session under the key usuario and issues a signed session cookie. Subsequent requests from the same browser include that cookie automatically, giving you access to protected views. There is no token to manage — authentication state lives entirely in the session.
Request
The email address associated with your ClimApp account. Must match a registered address exactly (case-sensitive).
Your account password. Minimum 6 characters. Passwords are stored as SHA-256 hashes; the plaintext value is never persisted.
Example request
-c cookies.txt flag saves the session cookie so subsequent curl requests can include it with -b cookies.txt.
Response
ClimApp responds with an HTTP redirect in both the success and failure cases. Inspect theLocation header to determine the outcome.
Success
- HTTP
302redirect to/(the dashboard). - The
Set-Cookieresponse header contains the signed session cookie. - A flash message with category
"success"is queued:"Login correcto.".
Failure — invalid credentials
- HTTP
302redirect back to/login. - A flash message with category
"error"is queued:"Email o contraseña incorrectos.". - No session cookie is set.
Session cookies are HTTP-only and signed by Flask’s secret key. Do not attempt to forge or decode them manually — Flask will reject any tampered cookie automatically.