<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Assumable Identities on</title><link>https://deploy-preview-3174--ornate-narwhal-088216.netlify.app/chainguard/administration/assumable-ids/</link><description>Recent content in Assumable Identities on</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><lastBuildDate>Thu, 16 Jan 2025 15:22:20 +0100</lastBuildDate><atom:link href="https://deploy-preview-3174--ornate-narwhal-088216.netlify.app/chainguard/administration/assumable-ids/index.xml" rel="self" type="application/rss+xml"/><item><title>Overview of Assumable Identities in Chainguard</title><link>https://deploy-preview-3174--ornate-narwhal-088216.netlify.app/chainguard/administration/assumable-ids/assumable-ids/</link><pubDate>Thu, 04 May 2023 08:48:45 +0000</pubDate><guid>https://deploy-preview-3174--ornate-narwhal-088216.netlify.app/chainguard/administration/assumable-ids/assumable-ids/</guid><description>Both chainctl and the Chainguard Console are useful tools for interacting with Chainguard. However, there may be times that you want to hand off certain administrative tasks to an automation system, like Buildkite or GitHub Actions.
In such cases, you can create a Chainguard identity for these systems to assume, allowing them to perform certain tasks within a specific scope. You can restrict access to an identity so that only workflows that present tokens matching a specific issuer and subject can assume it.</description></item></channel></rss>