<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Authentication on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/authentication/</link><description>Recent content in Authentication on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 19 Oct 2026 17:18:05 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/authentication/index.xml" rel="self" type="application/rss+xml"/><item><title>GitHub may require auth for unauthenticated HTTPS clones during high traffic</title><link>https://curadevops.metacog.co.kr/insights/2026-10-19-some-git-over-https-may-temporarily-require-authentication/</link><pubDate>Mon, 19 Oct 2026 17:18:05 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-10-19-some-git-over-https-may-temporarily-require-authentication/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> Infrastructure automation (Terraform module fetches, Helm chart pulls, init containers) that clones public GitHub repos over unauthenticated HTTPS could intermittently fail; audit and add GitHub credentials to affected workflows.&lt;/li>
&lt;li>&lt;strong>CI/CD — Plan:&lt;/strong> Pipelines cloning public GitHub repos over unauthenticated HTTPS risk intermittent checkout failures; audit all pipeline steps using unauthenticated HTTPS and switch to authenticated HTTPS (GITHUB_TOKEN) or SSH to ensure reliability.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item><item><title>AWS Lambda adds OAuth support for self-managed Kafka event sources</title><link>https://curadevops.metacog.co.kr/insights/2026-10-10-aws-lambda-supports-oauth-authentication-for-self-managed-ap/</link><pubDate>Sat, 10 Oct 2026 16:03:07 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-10-10-aws-lambda-supports-oauth-authentication-for-self-managed-ap/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Learn:&lt;/strong> Newly GA OAuth support for Lambda Kafka ESM unblocks regulated-industry workloads that couldn&amp;rsquo;t use SASL/PLAIN or mTLS; worth noting if the team runs Kafka clusters consumed by Lambda, but no existing configuration needs to change.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item><item><title>AWS Batch gains EKS access entry authentication support</title><link>https://curadevops.metacog.co.kr/insights/2026-10-06-aws-batch-now-supports-amazon-eks-access-entry-authenticatio/</link><pubDate>Tue, 06 Oct 2026 17:01:10 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-10-06-aws-batch-now-supports-amazon-eks-access-entry-authenticatio/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> If you run AWS Batch compute environments on EKS, you can now migrate from the aws-auth ConfigMap to the newer access entry API for IAM-principal authentication; schedule an UpdateComputeEnvironment pass to set accessEntry.desiredState=ENABLED, simplifying auth lifecycle management on those clusters.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item><item><title>GitHub App installation tokens now fully stateless format</title><link>https://curadevops.metacog.co.kr/insights/2026-10-03-stateless-github-app-installation-tokens-rolled-out/</link><pubDate>Sat, 03 Oct 2026 15:01:20 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-10-03-stateless-github-app-installation-tokens-rolled-out/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Learn:&lt;/strong> Infrastructure automation using GitHub App tokens (e.g., Flux, Argo CD, Terraform GitHub provider) should still work without changes, but teams relying on token introspection or format-specific parsing should verify compatibility with the new stateless format.&lt;/li>
&lt;li>&lt;strong>CI/CD — Plan:&lt;/strong> The rollout is complete, so all newly minted GitHub App installation tokens already use the stateless format; audit any pipeline code or tooling that parses or makes structural assumptions about token format to confirm nothing breaks.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>