bug(gotrue): stateless SignOut can only log out globally

Open Beginner friendly
#440 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
82/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
csharp
Domain
authentication

Research direction

Start with packages/Gotrue/Gotrue/StatelessClient.cs at StatelessClient.SignOut and follow its call into packages/Gotrue/Gotrue/Api.cs at Api.SignOut. Compare these with Client.SignOut(SignOutScope) and the IGotrueStatelessClient documentation. Done means stateless sign-out can request the local scope and its documentation no longer says it always revokes all refresh tokens.

Written by the indexing model from the issue text.

Description

Ran into this signing users out server-side. I wanted local and there's no way to ask for it.

await client.SignOut(accessToken, options);
// POST /logout?scope=global

StatelessClient.SignOut calls Api.SignOut(accessToken) with no scope, and Api.SignOut always writes ?scope= from its default. The stateful Client.SignOut(SignOutScope) takes one.

#148 closed as "Available in >= Supabase.Gotrue@5.0.6" but missed the stateless client, and its doc still says "This will revoke all refresh tokens for the user."

Dominant language
C#
Stars
701
Forks
106
Avg merge
16h 35m
Merged PRs (30d)
45

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from supabase/supabase-csharp

All issues in supabase/supabase-csharp

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.