A separate application containing its own template has been added to manage the 2fa functionality.
This model is linked to the user by a 'OneToOne' key. Automation of the initialisation of the separate table is correctly executed as soon as a new user arrives.
The user can activate and deactivate the 2fa function correctly.
By default 2fa is false.
When the user chooses to activate 2fa :
-> A correct route is created to generate a displayable qrcode in an html file and then it is disconnected from the site.
-> A token is sent to the next connection which must be taken to redirect the user to the correct view in order to confirm the code.
New functionality implemented:
A separate application containing its own template has been added to manage the 2fa functionality.
This model is linked to the user by a 'OneToOne' key. Automation of the initialisation of the separate table is correctly executed as soon as a new user arrives.
The user can activate and deactivate the 2fa function correctly.
By default 2fa is false.
When the user chooses to activate 2fa : -> A correct route is created to generate a displayable qrcode in an html file and then it is disconnected from the site. -> A token is sent to the next connection which must be taken to redirect the user to the correct view in order to confirm the code.