Skip to content

Keep custom public PKCE client_id in OAuth authorization code - #3012

Open
Hashim1999164 wants to merge 2 commits into
snowflakedb:mainfrom
Hashim1999164:fix/oauth-public-pkce-client-id
Open

Hashim1999164 wants to merge 2 commits into
snowflakedb:mainfrom
Hashim1999164:fix/oauth-public-pkce-client-id

Conversation

@Hashim1999164

@Hashim1999164 Hashim1999164 commented Sep 1, 2026 •

Copy link
Copy Markdown

Fixes #3011

The eligibility check treated a missing client_secret as a reason to replace a supplied client_id with LOCAL_APPLICATION. Public PKCE clients keep the custom client_id, skip HTTP Basic, and send client_id in the token request body.

Test plan

Ran pytest test/unit/test_auth_oauth_auth_code.py and test/unit/test_auth_oauth_credentials.py locally (34 passed).

@Hashim1999164
Hashim1999164 requested a review from a team as a code owner September 1, 2026 17:32
@Hashim1999164

Copy link
Copy Markdown
Author

I have read the CLA Document and I hereby sign the CLA

@Hashim1999164

Copy link
Copy Markdown
Author

recheck

@Hashim1999164
Hashim1999164 force-pushed the fix/oauth-public-pkce-client-id branch from a4112e5 to ecefd6f Compare October 2, 2026 21:32
@Hashim1999164

Copy link
Copy Markdown
Author

rebased onto latest main. kept the public PKCE client_id fix and slotted the DESCRIPTION note under v4.8.0.

This branch has not been deployed

No deployments
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.

SNOW-4036712: OAuth Authorization Code flow replaces custom public PKCE client_id with LOCAL_APPLICATION

1 participant