<?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 mishraJi</title>
    <link>https://blog.mishraji.org/tags/oidc/</link>
    <description>Recent content in OIDC on mishraJi</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 27 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://blog.mishraji.org/tags/oidc/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Workload Identity Federation</title>
      <link>https://blog.mishraji.org/posts/workload-identity-management/</link>
      <pubDate>Thu, 27 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://blog.mishraji.org/posts/workload-identity-management/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;A GitHub Actions pipeline needs to deploy resources into an AWS account. Before AWS will accept the API calls, the pipeline has to prove who it is.&lt;/p&gt;&#xA;&lt;p&gt;For a long time the answer was a static credential. You created an IAM user in AWS, generated an access key for it, and pasted the key ID and secret into GitHub Secrets.&lt;/p&gt;&#xA;&lt;figure&gt;&lt;img src=&#34;https://blog.mishraji.org/posts/workload-identity-management/images/figure1-static-credential.png&#34;&#xA;    alt=&#34;A GitHub Actions workflow authenticating to AWS with a static access key stored in GitHub Secrets.&#34;&gt;&lt;figcaption&gt;&#xA;      &lt;p&gt;A GitHub Actions workflow authenticating to AWS with a static access key stored in GitHub Secrets.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
