Describe the bug
A clear and concise description of what the bug is.
After logging out from a Supabase CLI account and logging in with a different account, it is still possible to affect the projects linked by the previous account.
To Reproduce
Steps to reproduce the behavior:
Run supabase login with Account A.
Use supabase link to link a project.
Execute supabase logout to log out.
Run supabase login with Account B.
Try to perform operations on the project linked by Account A.
See the issue where operations on the project linked by Account A are still possible.
Expected behavior
When logging in with Account B after logging out from Account A, operations on projects linked by Account A should be restricted.
System information
Version of OS: macOS Sonoma 14.5
Version of CLI: 1.187.10
Version of Node.js: v18.19.1
Chip: Apple M2
Model: MacBook Pro (Model Identifier: Mac14,7)
Docker:
Version: 4.30.0 (149282)
Engine: 26.1.1
Compose: v2.27.0-desktop.2
Credential Helper: v0.8.1
Kubernetes: v1.29.2
Additional context
If applicable, add any other context about the problem here.
avallete
commented
2 months ago
Describe the bug A clear and concise description of what the bug is.
After logging out from a Supabase CLI account and logging in with a different account, it is still possible to affect the projects linked by the previous account.
To Reproduce Steps to reproduce the behavior:
supabase loginwith Account A.supabase linkto link a project.supabase logoutto log out.supabase loginwith Account B.Expected behavior When logging in with Account B after logging out from Account A, operations on projects linked by Account A should be restricted.
System information
Additional context If applicable, add any other context about the problem here.