Add state parameter support for server-side OAuth CSRF protection #116
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.
This allows developers to:
Tested with ASP.NET Core application - state parameter now appears in OAuth URLs and is accessible via ProviderAuthState.State property.
Fixes supabase-community/supabase-csharp#222
What kind of change does this PR introduce?
Feature - Adds state parameter support for OAuth CSRF protection
What is the current behavior?
Currently, the SDK only supports PKCE flow for OAuth authentication, which protects against authorization code interception but does NOT protect against CSRF attacks in server-side OAuth flows.
The
SignInOptionsclass lacks aStateproperty, andProviderAuthStatedoes not return a state value. This makes it impossible for server-side ASP.NET Core applications to implement CSRF protection as recommended by OAuth2 RFC 6749 Section 10.12.Related issue: supabase-community/supabase-csharp#222
What is the new behavior?
This PR adds support for the OAuth2
stateparameter:Changes Made
Stateproperty toSignInOptionsStateproperty toProviderAuthStatereturn valueHelpers.GetUrlForProvider()to use developer-provided state or auto-generate usingGenerateNonce()Usage Examples
Server-side with CSRF protection: