Thanks for the great tutorial! Really simple explanation of supabase. There is an error that appears in your console after implementing the email display. How can this be fixed? Also: This authorization confirms that any person is logged in, how do we implement a specific user being logged in. For example, implementing a user settings page that should be private, only accessible for a given user
Hey. Great content about Vue! I see you work only with composition API and on your site is a mix of Options API and Composition API. It would be great if there would be two separate documentations one for Options API and one for Composition API. I really like Vue but at the same time I also hate Composition API :)
Great video! I love how you're just speaking normally, ie it doesn't sound like you're reading verbatim from a script like other Vue tutorials. Thank you, keep the videos coming! :)
Thanks for the video. Could you make a video about guards with different rolles. I cant find any tutorial about that. So a admin sees different pages then a editor etc. I fixed the login out with refresh by checking if there still is a supbase token stored. Apperently you can give the generasted token a name with storagekey and i just check if it exists.This works great.
Having a problem with keeping the user logged in after refreshes or closing the browser? Instead of await supabase.auth.getSession(); try this instead: import { useSupabaseUser } from "~~/.nuxt/imports"; const user = useSupabaseUser();
@@VueReference Hey thanks, that very much helped and it works! I thought I had to use something like Pinia because I saw that in another tutorial on Supabase auth but it seems not
We recently switched to Vue (nuxt) at work and although the switch was pretty smooth coming from react but I had an issue overwriting values defined with reactive, this definitely explains alot…thanks
Even though I use NextJS, I found this tutorial to be very useful in navigating Superbase. Do you see any security flaws in Superbase, i.e. I believe tokens are stored in local storage? Thx.
Supabase is opensource and as far as I know, no one as alerted to huge security vulnerabilities. In term of local storage, the token doesn't reveal anything that put's the user's security at risk. If a hacker had access to that user's computer, then they'd already know their email which is the only info in that token I would think is revealing in anyway. Having said that, I'm no security expert but I don't think storing JWT in local storage is the MOST secure way to go about things. Here's a nice stack overflow article that talks more about local storage vulnerabilities: stackoverflow.com/questions/44133536/is-it-safe-to-store-a-jwt-in-localstorage-with-reactjs Thanks for the comment!
