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
Currently if we want to revoke someones access, we have to tell the rfid device to remove everyone and then add everyone back.
This is not ideal because we have no verification that the rfid device received everyone.
We had a good system that verified that the access list on the rfid matched what we had in the DB. However, we switched to using esp-rfid and we no longer have this.
In the previous verification process, the rfid device would hash the list of rfid UIDs that have access and the server would verify that this hash was correct. If incorrect, the server would send an update to the rfid device.
The text was updated successfully, but these errors were encountered:
Currently if we want to revoke someones access, we have to tell the rfid device to remove everyone and then add everyone back.
This is not ideal because we have no verification that the rfid device received everyone.
We had a good system that verified that the access list on the rfid matched what we had in the DB. However, we switched to using esp-rfid and we no longer have this.
In the previous verification process, the rfid device would hash the list of rfid UIDs that have access and the server would verify that this hash was correct. If incorrect, the server would send an update to the rfid device.
The text was updated successfully, but these errors were encountered: