fix: enable es256 jwt signing algorithm support for gotrue #4489
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
bug fix
gotrue rejects es256 signed jwts with "signing method es256 is invalid" error despite proper signing key configuration in config.toml. the issue occurs because gotrue defaults to only accepting hs256 tokens without explicit algorithm configuration.
gotrue now receives gotrue_jwt_valid_methods environment variable during startup with all configured signing algorithms (hs256, rs256, es256). the fix detects algorithms from signing keys configuration and automatically includes them in the valid methods list. hs256 is always included for backward compatibility.
resolves #4488