<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>OAuth - Tag - AWS Sensei</title><link>https://aws-sensei.cloud/tags/oauth/</link><description>OAuth - Tag - AWS Sensei</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Wed, 01 Jul 2026 00:00:00 +0200</lastBuildDate><atom:link href="https://aws-sensei.cloud/tags/oauth/" rel="self" type="application/rss+xml"/><item><title>LinkedIn OAuth Tokens Expire Every 60 Days — Here's the Serverless Re-Auth Fix</title><link>https://aws-sensei.cloud/posts/2026-07-01-linkedin-oauth-reauth/</link><pubDate>Wed, 01 Jul 2026 00:00:00 +0200</pubDate><author>Marcel</author><guid>https://aws-sensei.cloud/posts/2026-07-01-linkedin-oauth-reauth/</guid><description>🔊 Voiced by Amazon Polly
The automated LinkedIn pipeline I built a few weeks ago worked well — until it would quietly stop working after 60 days. LinkedIn access tokens expire. And unlike most OAuth providers, LinkedIn does not issue refresh tokens to standard developer apps. When the token expires, posts stop.
This is the breakdown of the fix: a one-click re-authorization flow that takes about 30 seconds and runs entirely on AWS.</description></item></channel></rss>