Luckily, I’ve never faced an issue like this, but it came to my mind.

Let’s consider tokens or QR access tickets. Do I have any option rather than banning the ID on the server?

If I have a one-time-only access system with multiple entrances and I have no option to communicate one entrance with another one, what options may I have to prevent an user to duplicate his access ticket and give the second to another person?

I thought about forcing a person to enter only on one entrance and I could place an ID on the ticket that matches the entrance number, but this is not proper.

  • 1
    If you have multiple entrances, no way to prevent duplicates, and no way for your separate entrances to communicate, then you cannot prevent entries on duplicate tickets. Laws of logic are not your friend here. – Conor Mancone Feb 21 at 22:09

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.