GitHub
github.com › google-github-actions › auth
GitHub - google-github-actions/auth: A GitHub Action for authenticating to Google Cloud. · GitHub
Workload Identity Federation is ... a long-lived credential and establishes a trust delegation relationship between a particular GitHub Actions workflow invocation and permissions on Google Cloud....
Starred by 1.3K users
Forked by 293 users
Languages TypeScript 98.8% | JavaScript 1.2%
Videos
25:40
How to Setup Google Cloud Workload Identity Federation for GitHub ...
11:33
How to use Github Actions with Google's Workload Identity Federation ...
12:11
Stop Struggling—The Easiest Way to Get Secure GCP Access from ...
TERRAFORM AUTOMATION with GitHub and GCP Workload Identity Federation ...
Access Google Cloud from GitHub Action Sans Keys ...
GitHub OIDC and Google Identity Federation - YouTube
Databricks
docs.databricks.com › local development tools › authentication › authenticate using oauth token federation › enable token federation for ci/cd › github actions
Enable workload identity federation for GitHub Actions | Databricks on AWS
5 days ago - Subject claim: (Optional) The JWT claim that contains the workload identity (sub) value from the OIDC token. For GitHub, leave the field as sub, which encodes the repository, branch, tag, pull/merge request, or environment that triggered the workflow. To authenticate as a reusable workflow rather than the calling repository, see Authenticate using a reusable workflow. For example, the following Databricks CLI command creates a federation policy for an organization named my-org and a Databricks service principal numeric ID of 5581763342009999:
Google
docs.cloud.google.com › iam › identity and access management (iam) › configure workload identity federation with deployment pipelines
Configure Workload Identity Federation with deployment pipelines | Identity and Access Management (IAM) | Google Cloud Documentation
After you configure a workload identity pool to trust your GitHub repository, you can let workflows in that repository use their GitHub OIDC token to obtain short-lived Google Cloud credentials. You don't need to make any configuration changes in your GitLab account. After you configure a workload identity pool to trust your GitLab group, you can enable Workload Identity Federation for individual CI/CD jobs.
Google Cloud
cloud.google.com › blog › products › identity-security › enabling-keyless-authentication-from-github-actions
Enabling keyless authentication from GitHub Actions | Google Cloud Blog
December 7, 2021 - Whereas a JSON service account key is either accessible or inaccessible, Workload Identity Federation can be configured to selectively allow authentication based on properties in the downstream OIDC tokens. For GitHub Actions, that means you can, for example, restrict authentication to certain repositories, usernames, branch names, or published claims.
GitHub
github.com › aip-dev › google.aip.dev › blob › master › aip › auth › 4117.md
External Account Credentials (Workload Identity Federation)
In order to use workload identity ... are needed to configure workload identity pools, providers, service account impersonation and generate the JSON configuration file to be used by the auth libraries....
Author aip-dev
GitHub
github.com › pfnet-research › gcp-workload-identity-federation-webhook
GitHub - pfnet-research/gcp-workload-identity-federation-webhook: This webhook is for mutating pods that will require GCP Workload Identity Federation access from Kubernetes Cluster.
This webhook is for mutating pods that will require GCP Workload Identity Federation access from Kubernetes Cluster. - pfnet-research/gcp-workload-identity-federation-webhook
Starred by 50 users
Forked by 15 users
Languages Go 86.6% | Makefile 9.1% | Smarty 3.0% | Dockerfile 1.3% | Go 86.6% | Makefile 9.1% | Smarty 3.0% | Dockerfile 1.3%
GitHub
github.com › Azure › azure-workload-identity
GitHub - Azure/azure-workload-identity: Azure AD Workload Identity uses Kubernetes primitives to associate managed identities for Azure resources and identities in Azure Active Directory (AAD) with pods. · GitHub
Azure AD Workload Identity is the next iteration of Azure AD Pod Identity that enables Kubernetes applications to access Azure cloud resources securely with Azure Active Directory based on annotated service accounts.
Starred by 335 users
Forked by 108 users
Languages Go 90.1% | Shell 4.7% | Makefile 3.7%
GitHub
github.com › salrashid123 › workload_federation_cloudrun_gcf
GitHub - salrashid123/workload_federation_cloudrun_gcf: Authenticating using Workload Identity Federation to Cloud Run, Cloud Functions · GitHub
Configure GCP Workload Identity with that OIDC provider · Deploy a Cloud Run application which requires Authentication. Use Workload Federation and IAM API to exchange the ambient OIDC token from step 1 for a Google-issued OIDC token
Author salrashid123
GitHub
github.com › signalfx › gcp_workload_identity_federation
GitHub - signalfx/gcp_workload_identity_federation · GitHub
This repository provides tools to set up Workload Identity Federation in Google Cloud Platform (GCP) for granting access to Splunk integrations.
Starred by 2 users
Forked by 2 users
Languages Python 53.8% | HCL 46.2%
GitHub
github.com › MicrosoftDocs › entra-docs › blob › main › docs › workload-id › workload-identity-federation.md
entra-docs/docs/workload-id/workload-identity-federation.md at main · MicrosoftDocs/entra-docs
Set up a user-assigned managed identity as a federated identity credential on an app registration. Read the workload identity overview to learn how to configure a Kubernetes workload to get an access token from Microsoft identity provider and ...
Author MicrosoftDocs
DEV Community
dev.to › massimobonanni › azure-workload-identity-federation-and-github-actions-pf7
Azure Workload Identity Federation and GitHub Actions - DEV Community
May 2, 2023 - This approach was born to trust tokens from external identity provider, such as GitHub or Google (or other in the future). You first create a relationship between the identity (that can be a managed identity or an App registration) and the external identity provider. Once this relationship is created, every time the workload wants to authenticate itself against AzureAD, it retrieves a token from the external IdP and, uses it to request access token from AAD.
