Skip to content

chore(cloudflare): drop fork OAuth Basic D1 schema patch - #21

Closed
omega-alpha-matt[bot] wants to merge 1 commit into
mainfrom
chore/drop-oauth-basic-fork-patch
Closed

omega-alpha-matt[bot] wants to merge 1 commit into
mainfrom
chore/drop-oauth-basic-fork-patch

Conversation

@omega-alpha-matt

Copy link
Copy Markdown

Confirmed: upstream v1.6.8 already supports HTTP Basic client authentication for registered OAuth apps (client_secret_basic, plus basic_raw for providers that reject form-encoded credentials). The SDK, API, React form, and cloud/local drizzle migrations on this fork already match that release — those product commits were not replayed in the v1.6.8 sync.

The only remaining fork copy was a Cloudflare D1 compatibility ALTER that added oauth_client.token_endpoint_auth_method. This drops it so the Workers host matches upstream.

Production D1 already has the column from earlier deploys of the fork patch; new tables get it from FumaDB core-schema. The Access service-token subject mapping is unrelated and stays.

Verified

  • apps/host-cloudflare data-migrations tests (4)
  • git diff v1.6.8 -- apps/host-cloudflare/src/db/data-migrations.ts is empty

Upstream v1.6.8 already stores token_endpoint_auth_method and authenticates
confidential clients with HTTP Basic. The Cloudflare ALTER was the last
remaining fork copy of that work.

Co-authored-by: Matt Hodgson <matthodgson@mac.com>
@omega-alpha-matt

Copy link
Copy Markdown
Author

Closing: this only dropped the Cloudflare D1 ALTER. The v1.6.8 sync skipped the UsefulSoftwareCo#1448 token-auth commits (interoperable client_secret_basic, D1 schema, refresh threading) instead of rebasing them. Restoring that behavior on a new branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants