This shows you the differences between two versions of the page.
iothings:laboratoare:2022:lab4 [2025/03/20 16:49] andreea.miu Add explicit version for node.js |
iothings:laboratoare:2022:lab4 [2025/03/20 18:30] (current) andreea.miu [Exercise 1] email authorisation info |
||
---|---|---|---|
Line 278: | Line 278: | ||
=== Setting Up DB Security Rules === | === Setting Up DB Security Rules === | ||
- | As you can probably notice in the previous exercise, you can only save the last recording of your data. If we want to log multiple readings for our data and also guarantee that our data is more or less secure, we will need to configure the Firebase DB. | + | As you can probably notice in the previous exercise, you can only save the last recording of your data. If we want to log multiple readings for our data and also guarantee that our data is more or less secure, we will need to configure the Firebase DB. |
+ | |||
+ | On the Authentication tab, select Sign-in method > Sign-in providers > Add new provider. From this tab, select Email/Password provider, which will allow logging in the database through email. To authorise your email for logging in, from the same tab select Users > Add user, and input your email and password. This action will generate a user UID associated with your data. | ||
On the Realtime Database tab, select the Rules tab at the top. Then, click on Edit rules, copy the following rules and then click Publish. | On the Realtime Database tab, select the Rules tab at the top. Then, click on Edit rules, copy the following rules and then click Publish. |