Conference Session

Join the Zoom Event

Description

The University of Wisconsin-Madison is a large place, with many staff members. One of the struggles that is familiar to many is how to balance specialized needs for divisions, colleges and other groups inside the university, with the administrative goals of simplifying services at a central level. In particular, email transmissions that are handled by software without the intervention of human hands can struggle when modernization occurs: the need for multi-factor authentication and deprecation of POP/IMAP protocols conflicts with services run by groups such as the college of Engineering.

My presentation goes over the journey I made as the sysadmin for a ticketing program that needed to be able to fetch and send emails through O365 as a computer — not a human that could perform multi-factor auth. I will discuss the basic layout of the way that I solved the issue, point out some pitfalls that arise because of the University’s bureaucracy and hierarchical structure, and offer some tips for others trying to write middleware in the trenches.

My audience will understand this better if they know the underlying mechanisms of emails and how they’re sent or accessed, as well as Office 365 authentication mechanisms.

The key takeaways are that writing middleware or API layers at the University can be quite difficult and challenging, but given the right circumstances, also successful. Another thing to learn is that challenges are almost never purely technical in nature, a lot of obstacles that come up are going to include tasks that take people-knowledge and social skill in the workplace. An appreciation for the wide variety of business needs among campus IT will be emphasized strongly.

Presenter Information

• Brian Wilt

Image Licensed under Creative Commons Zero.