summaryrefslogtreecommitdiffstats
path: root/ogcp/templates/actions/image_restore.html
diff options
context:
space:
mode:
authorJose M. Guisado <jguisado@soleta.eu>2021-03-05 11:06:11 +0100
committerJose M. Guisado <jguisado@soleta.eu>2021-03-05 11:47:27 +0100
commit9ee0565ac41661a0521630fbfe1ea9e896fcec52 (patch)
tree12dd36a028ed7f9795855c599b2a05b76e058c01 /ogcp/templates/actions/image_restore.html
parent149dfdcbfd31bae79e9872e6f465d127d70ad32b (diff)
Add login
Ogcp requires a simple login page in order to avoid exposure of the ogServer API to anyone trying to access the web page. Because the main authorization mechanism in ogServer is the api token the login implemented for the ogcp does not include registration process but a single user and password specified in the ogcp.json. "USER": "user", "PASS": "pass" Adds two new views: /login and /logout. They are used to login the user so that the rest of views regarding ogServer functionality can be accessed in a "login required" fashion. Index view (/) is an exception, it can be accessed logged in or not so different data can be displayed. Templates can now access a variable "current_user" to get information about login status. This is a Flask-Login feature. - Templates regarding login can be found in templates/auth/ - Login form is defined in forms/auth.py to separate it from action_forms.py - Adds Flask-Login module to requirements.txt - Adds default user and pass in ogcp.json
Diffstat (limited to 'ogcp/templates/actions/image_restore.html')
0 files changed, 0 insertions, 0 deletions