Skip to content

fix: ignore not found error to check for pkce prefix later #1929

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 30, 2025

Conversation

kangmingtay
Copy link
Member

What kind of change does this PR introduce?

  • POST /verify fails for email change when PKCE is used and GOTRUE_MAILER_SECURE_EMAIL_CHANGE_ENABLED is enabled because the query to retrieve the token returns an error if the token is not found instead of trying again with the pkce_ prefix

@kangmingtay kangmingtay requested a review from a team as a code owner January 29, 2025 18:22
@coveralls
Copy link

Pull Request Test Coverage Report for Build 13037852442

Details

  • 1 of 1 (100.0%) changed or added relevant line in 1 file are covered.
  • 2 unchanged lines in 1 file lost coverage.
  • Overall coverage increased (+0.02%) to 65.6%

Files with Coverage Reduction New Missed Lines %
internal/models/one_time_token.go 2 69.05%
Totals Coverage Status
Change from base Build 13000101158: 0.02%
Covered Lines: 9863
Relevant Lines: 15035

💛 - Coveralls

@kangmingtay kangmingtay merged commit fbbebcc into master Jan 30, 2025
5 checks passed
@kangmingtay kangmingtay deleted the km/fix-pkce-verify-post branch January 30, 2025 20:54
kangmingtay pushed a commit that referenced this pull request Mar 6, 2025
🤖 I have created a release *beep* *boop*
---


##
[2.170.0](v2.169.0...v2.170.0)
(2025-03-06)


### Features

* improvements to config reloader, 100% coverage
([#1933](#1933))
([21c2256](21c2256))
* increase test coverage in conf package to 100%
([#1937](#1937))
([bc57c1c](bc57c1c))


### Bug Fixes

* enable SO_REUSEPORT in listener config
([#1936](#1936))
([a474b80](a474b80))
* ignore not found error to check for pkce prefix later
([#1929](#1929))
([fbbebcc](fbbebcc))
* log version & migration count
([#1934](#1934))
([8078cdc](8078cdc))
* update figma token endpoint
([#1952](#1952))
([18fbbb5](18fbbb5))
* use sys/unix instead of syscall
([#1953](#1953))
([4a6d9bc](4a6d9bc))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
wdoppenberg pushed a commit to wdoppenberg/supabase-auth that referenced this pull request Jun 5, 2025
wdoppenberg pushed a commit to wdoppenberg/supabase-auth that referenced this pull request Jun 5, 2025
🤖 I have created a release *beep* *boop*
---


##
[2.170.0](supabase/auth@v2.169.0...v2.170.0)
(2025-03-06)


### Features

* improvements to config reloader, 100% coverage
([supabase#1933](supabase#1933))
([21c2256](supabase@21c2256))
* increase test coverage in conf package to 100%
([supabase#1937](supabase#1937))
([bc57c1c](supabase@bc57c1c))


### Bug Fixes

* enable SO_REUSEPORT in listener config
([supabase#1936](supabase#1936))
([a474b80](supabase@a474b80))
* ignore not found error to check for pkce prefix later
([supabase#1929](supabase#1929))
([fbbebcc](supabase@fbbebcc))
* log version & migration count
([supabase#1934](supabase#1934))
([8078cdc](supabase@8078cdc))
* update figma token endpoint
([supabase#1952](supabase#1952))
([18fbbb5](supabase@18fbbb5))
* use sys/unix instead of syscall
([supabase#1953](supabase#1953))
([4a6d9bc](supabase@4a6d9bc))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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.

3 participants