Feature Update: App Login

To keep the mobile app secure, Amego has added new protections against unauthorized access and automated attacks. These protections greatly reduce the risk of brute-force login attempts.

With the new login process, there is a maximum of three verification attempts per code. After three failed attempts, the code no longer works, and a new code must be requested. To slow down repeated failures, exponential backoff is applied between attempts, so the wait gets longer after each failed attempt.

There are also limits on how often a new code can be requested. Attendees must wait at least ten seconds between code requests. If there have been failed attempts, they have to wait for the backoff period to end before requesting another code. When both are in effect, the longer wait time applies.

NEW: If an attendee can’t get their code

When an attendee can’t receive the verification email and code, it might be because of VPN restrictions or because they can’t get into their inbox. They can stop by the registration or help desk onsite.

Authorized staff can generate an Onsite Access Code from the attendee’s profile in Amego Admin. The attendee enters it in the app to log in. Each Onsite Access Code is created for one attendee, works once, and expires just like a standard code.