The Identity Verification Web Application consists of a Flask-based web server written in Python, utilizing various libraries. The application allows users to register, log in, and provides an admin panel for user management.

Technologies Used:

Python Libraries:
numpy
Flask
hashlib
face_recognition
base64
,...

Frontend Technologies:
HTML
CSS
Bootstrap
JavaScript

Features:
This project has the general introduction of the system on the first page and directs the user to the login and registration page.
On the registration page, after filling the required fields, the user takes a picture of himself with the device camera using the button provided in this form and records the information.
If the username is not duplicated and the fields are filled correctly, the user registration will be completed successfully. Passwords are securely hashed using hashlab for added security.
For login, both username and password are requested from the person for more security. Also, when logging in, a photo is taken by the device's camera and sent to the server along with the username and password information.
If the username is available in the table, the correctness of the password and then the correspondence of this image with the image registered during registration will be checked.
If the passwords and pictures match, the login will be done.
For this project, MySQL and users tables as well as user_location were used.
There is a field in the user table called flag, whose type is int, and we set its value to 0 in normal mode.
If the value of flag = 1, it means that the registered person is an admin.
Of course, by assigning different values, the amount of access can be changed.
The user_location table records the geographic point of people when they log in.
And the admin can see the list of users and these geographical points in the admin panel.
Currently, the accuracy of image authentication in this project is acceptable and it can even identify a person among a number of people for login. But the angle and distance to the camera must be suitable.
Of course, more features and security options can be considered depending on the user's needs, and the database and tables can also be different according to the user's needs.