From ad49df26d0b0c22ecb07e331f5b7c691f7901bad Mon Sep 17 00:00:00 2001 From: Logan Volkers Date: Wed, 23 Sep 2026 11:21:23 -0700 Subject: [PATCH] Update OIDC authentication section for clarity Removed note about OIDC authentication support for organization-level private registries. This no longer appreas to be true: https://github.blog/changelog/2026-04-14-dependabot-and-code-scanning-org-level-private-registries/ --- .../giving-org-access-private-registries.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/content/code-security/how-tos/secure-at-scale/configure-organization-security/manage-usage-and-access/giving-org-access-private-registries.md b/content/code-security/how-tos/secure-at-scale/configure-organization-security/manage-usage-and-access/giving-org-access-private-registries.md index b1b956322f1e..bea9de4800b9 100644 --- a/content/code-security/how-tos/secure-at-scale/configure-organization-security/manage-usage-and-access/giving-org-access-private-registries.md +++ b/content/code-security/how-tos/secure-at-scale/configure-organization-security/manage-usage-and-access/giving-org-access-private-registries.md @@ -106,9 +106,6 @@ See [AUTOTITLE](/code-security/how-tos/secure-your-supply-chain/manage-your-depe OIDC (OpenID Connect) authentication allows {% data variables.product.prodname_dependabot %} to use short-lived credentials from your cloud identity provider to access private registries, eliminating the need to store long-lived secrets. With OIDC, credentials are generated dynamically for each {% data variables.product.prodname_dependabot %} update job. You must configure a trust relationship between your cloud provider and {% data variables.product.github %} before {% data variables.product.prodname_dependabot %} can authenticate. -> [!NOTE] -> OIDC authentication for organization-level private registries is currently supported by {% data variables.product.prodname_dependabot %}. It is not supported by {% data variables.product.prodname_code_scanning %} default setup. - When you select **OIDC** as the authentication method for a private registry, choose one of the supported providers and fill in the required fields: * **Azure**: Enter the **Tenant ID** (Azure AD tenant ID) and **Client ID** (Azure AD application client ID). You must configure a federated credential in Azure AD that trusts {% data variables.product.github %}'s OIDC provider.