You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This means the flow should be as follows:
After loading the pos website, you are prompted with the same login as the dashboard. After logging in with your user account, you can log into one of the POS'es you own. Receiving a token for the POS that you just logged into. After logging into a POS, the normal keypad appears. Now product queries, and user queries should be made with the POS token, and the transaction should be made with the user token after the using the pin code.
Why is this needed?
Because then every user cannot get every other user anymore, and admins can no longer make admin request with their pin code, making the system more secure.
Other information
We should probably take the login screen logic away from the dashboard, and put this in some sort of common place.
The text was updated successfully, but these errors were encountered:
Is this a feature for the SudoSOS point of sale or for the SudoSOS dashboard?
Point of sale
What would you like?
We should implement the POS user authentication from GEWIS/sudosos-backend#62. As also described in GEWIS/sudosos-backend#232.
This means the flow should be as follows:
After loading the pos website, you are prompted with the same login as the dashboard. After logging in with your user account, you can log into one of the POS'es you own. Receiving a token for the POS that you just logged into. After logging into a POS, the normal keypad appears. Now product queries, and user queries should be made with the POS token, and the transaction should be made with the user token after the using the pin code.
Why is this needed?
Because then every user cannot get every other user anymore, and admins can no longer make admin request with their pin code, making the system more secure.
Other information
We should probably take the login screen logic away from the dashboard, and put this in some sort of common place.
The text was updated successfully, but these errors were encountered: