Repository navigation
DeepSeekBot Connect: register Microsoft and GitHub sign-in for UAT and Prod #2523
Description
Problem and context / 问题与背景
DeepSeekBot Connect sign-in offers Google and Apple. Microsoft and GitHub clients are not registered in UAT or Prod (.secrets/ has only google-oauth.env and apple-oauth.env). The runbook docs/agents/workos-social-login.md (PR #2492) has the steps.
Smallest useful scope / 最小有用范围
Register Microsoft (Entra app, personal accounts, web redirect from WorkOS, email/family_name/given_name claims, secret expiry recorded) and GitHub (one OAuth App per environment, user:email) clients for UAT and Prod. Enter them in WorkOS and store them in .secrets/microsoft-oauth.env and .secrets/github-oauth.env with UAT/PROD prefixes. The Human signs in to every console; never print secrets. Or decide not to offer them and turn them off in WorkOS.
How to verify / 如何验收
In a private window, deepseekbot connect-sign-in --wait succeeds with each new provider in Prod, and the phone app's sign-in shows the provider.
Activity
DoodleBears commentedon Oct 21, 2026
Closing as not planned: Vain decided Microsoft and GitHub sign-in aren't needed for DeepSeekBot Connect for now.
State checked in the TOB WorkOS project on 2026-10-21 (read-only, nothing changed): neither Staging (UAT) nor Production has a
MicrosoftOAuthorGithubOAuthcredential of our own. Google is configured with our own clients in both environments. If these providers are wanted later, reopen this issue and followdocs/agents/workos-social-login.md(PR #2492).Generated by Claude Code