<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Docker Hub on Cloudkaramchari</title><link>https://www.cloudkaramchari.com/tags/docker-hub/</link><description>Recent content in Docker Hub on Cloudkaramchari</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>cloudkaramchari</copyright><lastBuildDate>Sat, 08 Aug 2026 12:00:00 +0530</lastBuildDate><atom:link href="https://www.cloudkaramchari.com/tags/docker-hub/index.xml" rel="self" type="application/rss+xml"/><item><title>Docker Hub OIDC for GitHub Actions: Retire Your Stored Access Tokens</title><link>https://www.cloudkaramchari.com/blog/docker-hub-oidc-authentication-github-actions-no-more-stored-tokens/</link><pubDate>Sat, 08 Aug 2026 12:00:00 +0530</pubDate><guid>https://www.cloudkaramchari.com/blog/docker-hub-oidc-authentication-github-actions-no-more-stored-tokens/</guid><description>
&lt;h1 id="docker-hub-oidc-for-github-actions-retire-your-stored-access-tokens">Docker Hub OIDC for GitHub Actions: Retire Your Stored Access Tokens&lt;/h1>
&lt;p>If your CI pipeline pushes images to Docker Hub, there's a good chance a Personal Access Token (PAT) or Organization Access Token (OAT) is sitting in your GitHub repository secrets right now — valid for months, scoped broader than you'd like, and one leaked build log away from being someone else's problem. On July 31, 2026, Docker shipped OIDC connections for GitHub Actions, closing that gap the same way AWS and GCP closed it for cloud credentials years ago: workflows authenticate with a token that's minted per run and expires in minutes, so there's nothing sitting in secrets to steal or rotate.&lt;/p></description></item></channel></rss>