Allow session to be valid without refresh token provided #574
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.
What kind of change does this PR introduce?
Bug fix
What is the current behavior?
Now if provide only access token to the
set_session
method, client will be authenticated and configured, but consequent calls tosupabase.auth.get_sesion
orsupabase.auth.get_user
will returnNone
which is confusing.This is because current session is deleted from internal storage if its refresh key is absent (and most surprisingly this deletion happen from the
get_session
method). See here for details.But it is pretty convenient to create short sessions from access token only, and let some upstream app to manage these keys by itstelf.
Workaround:
Provide some dummy non-empty refresh token, e.g.
What is the new behavior?
supabase.auth.get_session
andsupabase.auth.get_user
returns session and user accordingly.See: