Firebase Auth Tutorial #10 - UI & Firestore Security Rules

preview_player
Показать описание
Hey gang, in this firebase auth tutorial I'll show you how we can conditionally show & hide content dependent on a user's authentication state. I'll also show you how to secure your data using firestore security rules.

----------------------------------------

🐱‍💻 🐱‍💻 Course Links:

🤑🤑 Donate


🎓🎓 Find me on Udemy

Рекомендации по теме
Комментарии
Автор

The "rules" tab of Database in Firebase always scares me. But you gave me the courage to fight against it. Thank you so much!

Cho
Автор

Yes! I've been waiting patiently for this lol. Keep up the great work. I've learned so much from all your series! 🤓

bobdpa
Автор

this stuff is good! absolute legend, thank you for putting this together it's helping me so much with what I need to do

nohammahon
Автор

Oooh! as awesome as ever! now i can't wait for the next video.

michongoma
Автор

I am not scared or intimidated by Firebase anymore. All thanks to you Shaun. Good job on this series, world-class quality content my friend. Greetings from South Africa

SimPwear
Автор

The video is amazing, but I found a loophole in one place,
Instead of checking the length of the data array, we should pass the user object directly to the setupGuides function, because it can happen that you are logged in but you dont have any data in your database. And your code will show "Login to view guides" in these cases also. By checking the user object for null, you can eliminate the issue, because user is null only when you aren't logged in, no relation to what's stores in the database.

pratyushbhatt
Автор

Dude sorry, as I keep dreaming more series from this "ninja pipeline of educational content".
Do you have any plan to create a "cloud function" series!? Things like compressing uploaded images and videos.

Long live the net ninja.

Greetings from Tanzania 🇹🇿

raymondmichael
Автор

Great video, I want to add to it that you should implement a simple `allow delete: if false;` or any condition you might want to use for that. If you leave the rules as they are here, anyone would have access to a delete request and delete your database.

Автор

Alhamdulillah dapat video seperti ini. thanks ninja.. awwww..

ridwanridiawan
Автор

You can take the firestore security rule to another level by doing:

*allow read, write: if request.auth != null && request.auth.uid == userId;*

This won't just give read and write access if the request auth id is not null, but rather it will check if that reqeuest auth id is equal to the userId.

Antnix
Автор

This is some awesome video serie. You deserve all your 439k + 1 subscribers.

alimertc
Автор

Loving the course so far! in your firebase series do you by chance show how to narrow this down even more? like having levels of membership or types? or would this just happen by breaking them out within the DB?

chrisconnelly
Автор

Quick question. What if I make a request with some uid I make up. It is not null, so I should get the data. Or does firebase somehow checks first if the uid is in auth list of uids?

BHFJohnny
Автор

how did you covered keep user signed in after reload?

LuckyStilet
Автор

Thank you, Senpai, for the wonderful tutorial. Just a tip to my co-Kohais out there, the best way to learn is to do this:

1. Watch the entire video and listen very carefully all through out. Try to remember everything.
2. Recreate the lesson in your local environment with the video playing in the background. Code as you listen. If you forget, look at the video.

This way you immerse in step 1 and you execute in step 2. Any issues encountered along the way will be a learning opportunity. Pretty effective, I must say.

ilustrado
Автор

Ninja, Do you know if I can read and fetch from user's Gmail account when they sign in with Google? I know Auth0 allows this but wasn't sure about Firebase Auth.

boshiij
Автор

at 10:30 do we have to hit publish in order for firebase to remember the new rules you wrote?

yadude
Автор

does it provide security that any session api provides?

imkronos_me
Автор

how did we get the "bookId" because it is a "books" collection?
So if it were a "authors" collection then this will be "authorId"?

shadmanmartinpiyal
Автор

so what is the plan here when we are setting up different routes? How do I set them on on 'onAuthStateChange'. In this tutorial guides are almost "hardcoded" into auth stage. Am I missing something?

arturmrozinski