I recently completed work on a large project at Intercom to migrate our Okta organization from a legacy custom HR integration to Okta’s built-in profile sourcing feature. I won’t bore you with every detail, but one of the most critical issues which prevented us from using profile sourcing in the past was the potential for an HR team member to input invalid data in our HRIS[1].

Continuing on in my webinar series, you can now see a fireside chat where I’ve met with Greg Lorenz at Okta to discuss Intercom’s experience as an early adopter of Okta Identity Engine.

Mastodon recently added a feature to add author attribution labels to links posted across Mastodon.

While making some small design changes to my website today, I noticed Safari on macOS was rendering a PDF at a very small scale, rather than filling the entire Safari window, as it usually does. After some troubleshooting, I realized Safari was generating a content security policy error, indicating the PDF itself was violating my site’s content security policy by trying to use unsafe-inline as its style-src.

As a follow-up to my earlier post about Tines featuring my recent work at Intercom, you can now see a webinar where I’ve discussed all of this work in depth with Kelli Hinteregger, Head of Product Marketing at Tines! 🎉

I’ve been doing some “spring cleaning” in AWS and GitHub related to yesterday’s post, and while I was digging around, I realized there was a way to update my blogging stack and finally move it off GitHub Pages and instead use an AWS S3 bucket behind CloudFront, just like all of of my other websites.

If, like me, you use AWS CloudFront as a CDN to host content stored in an S3 bucket, you might not necessarily want search engines to index that content. When researching a solution to this problem for myself, I found plenty of forum discussions and blog posts suggesting you can accomplish this with a simple robots.txt file stored at the root of your S3 bucket. Google’s robots.txt documentation warns against doing this, however:

I’m excited to announce that Tines has published a case study based on my recent work deploying it as a business process automation platform for IT, InfoSec, and the entire company at Intercom! 🎉

After years without a good solution to my “static AWS IAM user secrets” problem, I’ve recently set up Dynamic Provider Credentials for AWS in my Terraform Cloud org.

Hello Again 👋🏼