You need to implement this feature:
Anyone can browse the CFP collection. Only signed up members are allowed to download any
material hosted by CFP. The sign-up process requires the member to be introduces by an existing
member and requires the name, organization, address, primary email and an recovery email
address: the system also generates a matrix of characters which wold be used as a verification for
the authenticity of the user. This matrix has a life time and would be renewed before expiry.
I searched on the matrix implementation for verification and I found a good example:
Imagine when a user logs in, the system generates a 4x4 matrix (grid) of random characters:
A 7 D Q
F M 3 T
9 Z X B
K R W 1
The user is asked to provide a character from a specific position (e.g., row 2, column 3, which is "3") or use the matrix in another way for verification. The matrix expires after some time (e.g., 5 minutes), and a new matrix is issued upon the next login or authentication challenge. This approach makes it harder for an unauthorized person to authenticate even if they know the user’s password, as they would need the current valid matrix which is continuously updated.
On the frontend, you need to create and build Sign up and Log in UI pages as well.
You need to implement this feature:
Anyone can browse the CFP collection. Only signed up members are allowed to download any
material hosted by CFP. The sign-up process requires the member to be introduces by an existing
member and requires the name, organization, address, primary email and an recovery email
address: the system also generates a matrix of characters which wold be used as a verification for
the authenticity of the user. This matrix has a life time and would be renewed before expiry.
I searched on the matrix implementation for verification and I found a good example:
Imagine when a user logs in, the system generates a 4x4 matrix (grid) of random characters:
A 7 D Q
F M 3 T
9 Z X B
K R W 1
The user is asked to provide a character from a specific position (e.g., row 2, column 3, which is "3") or use the matrix in another way for verification. The matrix expires after some time (e.g., 5 minutes), and a new matrix is issued upon the next login or authentication challenge. This approach makes it harder for an unauthorized person to authenticate even if they know the user’s password, as they would need the current valid matrix which is continuously updated.
On the frontend, you need to create and build Sign up and Log in UI pages as well.