Authentication, The Third Culture
In today’s lecture, we talked about Tim Ticket’s visitor authentication method. On a concrete level, it asks for the user’s phone number. On a more conceptual level, it uses the number as a token for authentication. Some concerns associated with such authentication include that it is costly and can be simplified.
I can’t help but think back to when my roommate from last year first started cross-registering and tried to access campus. It was when CovidPass was still active. In order to gain access to campus buildings, she needed to put in her ID number in CovidPass. In order to log into Atlas, she needed to physically visit E17 and activate her student ID. This created a deadlock situation for her, because my ex-roommate did not feel comfortable going to E17 without a valid attestation in CovidPass. Desperate, she asked me to set up a Tim Ticket for her. I followed the instructions. When I saw “Valid” on the screen, I thought it was all set to go, only to find out that it still didn’t work for her when she tried to access campus. I did not know about the additional steps on the visitor’s side or the timed QR code until this lecture!
Authentication is a means of protecting people’s privacy and prevent data leak, yet it sometimes also makes things complicated. I remember when I was first setting up MIT Certificate and Duo. It was in the COVID year. As a third cultural kid, I moved around a lot and happened to be abroad in Shanghai during that time. With internet latency and VPN issues, I had to send multiple emails to eventually resolve it. This got me start thinking about where authentication and accessibility collide: is there a middle ground that the two could meet in?