Jammy's Cave

In Part 1, I explained the OAuth protocol flow at a high-level. In this part, we will dive in to the most popular authorization grant type: the authorization code grant. Grant Flow The authorization code grant is a redirection-based flow: The client redirects the resource owner’s user agent (hereafter, we’ll just say “browser”) to the authorization server. The authorization server authenticates the user. The authorization server asks the resource owner for consent to give the client access to the protected resources.

Let’s imagine I am working on a calendar app. I know that a lot of my users keep their events in Google Calendar, so I need to make sure that I can retrieve their events from Google, and send back the newly created ones. How does Google know that my app is allowed to access a user’s calendar? As a user, when I go to https://calendar.google.com I’m asked to provide the username and password for my Google Account.

In Part 1, I installed FreeBSD on my Dell XPS 13, configured wireless networking, and created a new boot environment. In this part, I’ll install some of the software that I need and start on the configuration of the system. Display Resolution When I bought this laptop, I opted for a variant with a QHD+ screen. In hindsight, I wish I hadn’t done that. While the HiDPI situation in Linux has improved over the past few years, the experience is still far from seamless, and the situation in Windows isn’t much better.

I like to think of myself as being fairly Operating System agnostic. At home, my main desktop runs macOS and my laptop runs OpenSUSE. At work, I develop software for a Debian-based network operating system and administer CentOS VMs on VMware hypervisors. There are two gaps here though. I don’t particularly use Windows any more (other than still rocking a Windows Phone for work), and I’ve never really seriously used a BSD.