ISE Blog

What we have to say, what you want us to hear.

That’s how our blog works. It’s interactive. Let’s learn together.

Jon Opdahl, Software Engineer

Jon Opdahl, Software Engineer
Jon Opdahl is a full-stack web developer and web technology practice lead at Innovative Software Engineering. He has been with ISE since June of 2017. Fascinated with JavaScript, he loves working with Node.js and front-end frameworks like React and Angular. He is passionate about designing meaningful software that engages users and drives business. Outside of work, he is an avid baseball and hockey fan and enjoys golfing and tennis, as well as spending time with his wife.

Recent Posts

Website Authentication – Part 2: Intro to OAuth 2.0

Mar 05, 2020 | by Jon Opdahl, Software Engineer | Tags: Web Development

In our last blog post on web authentication, we looked at the SAML protocol. While SAML provides the capability to manage user identity between applications, it has largely been replaced by the more flexible and lightweight OAuth 2.0 protocol, which is the focus of this and the following blog posts. 


If You Give a Dev a Cookie...

Feb 06, 2020 | by Jon Opdahl, Software Engineer | Tags: Web Development

In this blog post, we talk about what a cookie is in the context of web development, how websites and web services use cookies, and some of the pitfalls to watch out for when using cookies. Let’s get started!


Website Authentication – Part 1: SAML

Nov 26, 2019 | by Jon Opdahl, Software Engineer | Tags: Web Development

Ultimately, there comes a point in almost every application’s life where it needs to either protect resources, or access protected resources. This used to be solved by simple client-server authentication, where a resource owner (an end user who owns specific data hosted on a server) would exchange credentials with a server to gain access to protected resources.


Supporting Multiple Browsers in Web Applications

Oct 24, 2019 | by Jon Opdahl, Software Engineer | Tags: Web Development

Around this time last year, I was developing a website for my wedding. The primary function of this website was to have guests RSVP on the site, so we could save a little money on postage and letterhead. I performed a thorough set of testing scenarios on Chrome, Firefox, and Edge, even employing the browsers’ mobile simulators. Everything seemed to work fine, so we sent out the invites and waited for RSVPs.

About a week afterwards, I got a text from my aunt; she couldn’t submit her RSVP! Why didn’t I catch this flaw in my testing?