<?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 Gerard Samuel</title><link>https://gerardsamuel.me/tags/authentication/</link><description>Recent content in Authentication on Gerard Samuel</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Mon, 25 Nov 2024 13:20:59 -0500</lastBuildDate><atom:link href="https://gerardsamuel.me/tags/authentication/index.xml" rel="self" type="application/rss+xml"/><item><title>Google Cloud Workload Identities with GitLab</title><link>https://gerardsamuel.me/posts/how-to-configure-google-cloud-workload-identities-with-gitlab/</link><pubDate>Mon, 25 Nov 2024 13:20:59 -0500</pubDate><guid>https://gerardsamuel.me/posts/how-to-configure-google-cloud-workload-identities-with-gitlab/</guid><description>&lt;p&gt;Using JSON keys to authenticate with Google Cloud is highly frowned upon. Unless you have no other &lt;a href="https://cloud.google.com/iam/docs/best-practices-for-managing-service-account-keys" target="_blank" rel="noreferrer"&gt;option&lt;/a&gt;, Google Cloud provides a more secure means of authenticating externally executed code. My use case is for authentication in GitLab pipelines so that I can automate tasks. Think Terraform jobs or updating the files for a website stored in a Google Cloud storage bucket. I will use Google Cloud&amp;rsquo;s Workload Identity Federation solution and the OIDC (Open ID Connect) &lt;a href="https://openid.net/developers/how-connect-works/" target="_blank" rel="noreferrer"&gt;protocol&lt;/a&gt; in this solution.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://gerardsamuel.me/posts/how-to-configure-google-cloud-workload-identities-with-gitlab/featured.png"/></item></channel></rss>