<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>OIDC on</title><link>https://deploy-preview-3420--ornate-narwhal-088216.netlify.app/tags/oidc/</link><description>Recent content in OIDC on</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Copyright (c) 2023 Chainguard</copyright><lastBuildDate>Tue, 23 Dec 2025 15:04:05 +0100</lastBuildDate><atom:link href="https://deploy-preview-3420--ornate-narwhal-088216.netlify.app/tags/oidc/index.xml" rel="self" type="application/rss+xml"/><item><title>Octo STS Overview</title><link>https://deploy-preview-3420--ornate-narwhal-088216.netlify.app/open-source/octo-sts/overview/</link><pubDate>Tue, 23 Dec 2025 15:04:05 +0100</pubDate><guid>https://deploy-preview-3420--ornate-narwhal-088216.netlify.app/open-source/octo-sts/overview/</guid><description>&lt;p&gt;Octo STS is a GitHub App developed by Chainguard that acts as a Security Token Service (STS) for the GitHub API. It enables workloads running anywhere that can produce OIDC tokens to federate with GitHub, exchanging those tokens for short-lived GitHub access tokens. The primary goal is to eliminate the need for GitHub Personal Access Tokens (PATs), which are long-lived credentials that pose significant security risks.&lt;/p&gt;
&lt;h2 id="why-octo-sts-matters" class="heading-2" data-heading-level="2"&gt;
&lt;span class="heading-text"&gt;Why Octo STS Matters&lt;/span&gt;
&lt;a href="#why-octo-sts-matters" class="anchor" aria-label="Link to Why Octo STS Matters" title="Link to this section"&gt;
&lt;svg width="16" height="9" viewBox="0 0 16 9" fill="none" xmlns="http://www.w3.org/2000/svg" aria-hidden="true"&gt;
&lt;path d="M6.833 8.125H4C3 8.125 2.146 7.77067 1.438 7.062C0.729333 6.354 0.375 5.5 0.375 4.5C0.375 3.5 0.729333 2.646 1.438 1.938C2.146 1.22933 3 0.875 4 0.875H6.833V1.958H4C3.30533 1.958 2.708 2.208 2.208 2.708C1.708 3.208 1.458 3.80533 1.458 4.5C1.458 5.19467 1.708 5.792 2.208 6.292C2.708 6.792 3.30533 7.042 4 7.042H6.833V8.125ZM5.208 5.042V3.958H10.792V5.042H5.208ZM9.167 8.125V7.042H12C12.6947 7.042 13.292 6.792 13.792 6.292C14.292 5.792 14.542 5.19467 14.542 4.5C14.542 3.80533 14.292 3.208 13.792 2.708C13.292 2.208 12.6947 1.958 12 1.958H9.167V0.875H12C13 0.875 13.854 1.22933 14.562 1.938C15.2707 2.646 15.625 3.5 15.625 4.5C15.625 5.5 15.2707 6.354 14.562 7.062C13.854 7.77067 13 8.125 12 8.125H9.167Z" fill="currentColor"/&gt;
&lt;/svg&gt;
&lt;/a&gt;
&lt;/h2&gt;&lt;p&gt;Long-lived access tokens are a common target in security incidents. When attackers gain access to a PAT, they can exploit it to access repositories, make changes, and pivot to other resources. These tokens often have broad permissions and no expiration date, making them particularly dangerous if compromised.&lt;/p&gt;</description></item></channel></rss>