#6356 landed customer GitHub sign-in switched off. Its github-oauth
ExternalSecret has since synced the "Devantler Tech" GitHub App's
credentials in production (Ready, SecretSynced). This turns
CUSTOMER_GITHUB_SIGNIN on. The setup CronJob then registers the GitHub
provider in the Customers organization: invite-only, with no account
creation and email auto-linking only between verified addresses.
The Customers login policy keeps password and MFA, with MFA forced for
local sign-in only.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
What
This turns on customer GitHub sign-in. In the setup CronJob,
CUSTOMER_GITHUB_SIGNINgoes from"off"to"on". Nothing else changes.Why now
#6356 landed customer GitHub sign-in switched off, so its inputs could be validated in production first. They are, checked read-only after its deploy:
github-oauthExternalSecret isReadywith reasonSecretSynced, last synced 22:51 UTC. That is the public "Devantler Tech" GitHub App's client ID and secret, from OpenBaoapps/customer-identity/github-oauth.customer-identity-setup-29913060, 23:00 UTC) loggedcustomer GitHub sign-in is off (CUSTOMER_GITHUB_SIGNIN)and… customer_github=off no changes. The administrator's GitHub sign-in was untouched.What the next run does
It reconciles ZITADEL's native GitHub provider in the Customers organization, which was tested locally in #6356:
read:useranduser:email. The app's only permission is "Email addresses: read-only".The run logs
created the GitHub identity provider in the Customers organization, set the login policy of the Customers organization, and later runs reportno changes. The portal stays off, so customers can't reach this yet.Turning it off again needs the provider removed on purpose: while off, the run refuses a provider left in the Customers organization.
Part of devantler-tech/business-site#302.
🤖 Generated with Claude Code