Original subtitles

In the previous lecture, we have created the user module and we have dispatched the register action

from registered page in this lecture will work on the actual Firebase authentication of functionality.

Let's start up a new tab in your browser, or let's navigate to the Firebase console.

So let's find your firebase.

Firebase will go to the console, so we'll see how the application.

OK, so Firebase go to the console and they console, go to the ID tab console, find your project and

you probably already on the page they're exchanging.

Are you here?

And on the left hand side, you can see authentication, let's think of that dedication, have a different

strategies, you can get your authentication done.

But first, let's go here to get started.

OK, so get started and we can choose from the outer decorations here, how we would like to authenticate.

I will choose the other than normal one email and the password.

OK, so let's go with an email and a password.

Email and password will enable it.

And that's it.

Just save it.

OK, so save it, that's our provider, and we should see that it's enabled here in a password is enabled,

that's very important.

Authorized domains you can see here.

The authorized domains for these.

Is the local host here?

It's a very important to have your local hosts so we can test it out.

OK, so if it is, we can also go to the user types of animals, so when you click here on the users

on the left hand side, you will see it's empty.

We don't have any users, but after that, after this lecture, you should have here a couple of users.

It should work so.

They're going to use our module because that's where we need to handle the changes, we are sending

form data.

So now it's up to the user module to get this data and to work with them.

So I've got to use our module able to close all of the other files so they're not bothering us.

And first of all, important here, a couple of helper factions here, only two functions, so it's

important here I have curly brackets and let's back here, get out and also function.

Create a user with email and password, create user with email and password.

It's quite a long name and you need to import it from Firebase flesh out.

Like this, make sure it's spelled correctly.

It is correct you will see her errors that you will use these functions.

You can enable that email and a password to be donated and what the Arab world will be doing by the

first look that they're very able to look out and from obviously they'll start to get out this.

They should get us the object containing some functionalities related to our authentication of the Firebase.

That's what that's required.

Danny, go right here to try and catch block when you're working with the authentication, you would

like to wrap your functionality into tribe, so if something goes wrong, you are not grab your application,

but you will catch the error.

OK, so in try block, but you want to do is to call the function here, create user with email and

password.

This will be asynchronous function because it's returns promise civil like the register as a async function.

In a tribe blog, you will call her Create User ID, email, password your prefixes to evade to synchronize

it your buzzer out and email pasdar.

Also email and the password.

OK, so it looks like this evade, create user ID and password and you are passing that out.

It goes from here and the email and password we got from register.

OK, and that's basically down the road to skin color here.

That's something that we have been successful.

So we've got here, there's been success at your user use.

There has been a registered user has been registered.

OK, by the way, from dysfunctional venues that was registered, you're getting something called user

credentials to convert your user credentials because their credentials and from these are conventions,

you can extract the user itself.

So the user have just registered so you can return from here.

User credentials dot the user.

In the catch you below, you will get error so you can check for error here and just simple of an ad

or Hepburn just console.log it down to just console a console error that something went wrong in the

error message.

Oh, OK, so just guys, to recapitulate a legislative function that is very simple, it forbids the

only things you need is our.

All right, and the function cleared to use their email and the password, create user with email and

password.

Accepting the out, you get here and email the password from your forum you will sent here.

If everything is geared to your ID and fighter bases and about, you should be able to create the user

and Firebase will return to you user credentials.

So basically information about the user you have just added into the Firebase that it'll already alert

this capability to the user credentials of the user if something goes wrong here in this function.

Specifically, this function, so you'll provide the drug out here, or they will provide something

some wrong data.

Then this will fail and they will jump into the catch block, cage or block.

The therapies will pass you.

The error object and error object contains a message properly, and the message properly is a description

of the error you are getting.

So that's what's happening here.

OK, let's save it.

Go to a better browser and let's try to register users so any email you want, so I let her test at

the Gmail dot com.

Now about your password test.

That's I will say, eloquent here.

Sign up.

OK.

And actually, the user has been registered to have slow internet, so it took a while about registering.

We could also display here are some loader acorn and disabled buttons, but we will handle it later.

But the user has been registered, which is good.

But it will go here to exchange a refresh on the user top.

And I should have here my first user, I have just registered.

That should be this test user.

So let's wait for a fresh.

OK.

Take some time, and we have here.

That's the Gmail dot com providers means email on a password created, signed in, and here is my user

ID.

So some unique identifier of the user that has been auto generated for me and that's my user.

It's working.

They can also debug it for a second user.

So you'll see what we are getting here.

Debugger.

You can go here and I will just simply refresh.

And open here, and I will write you the password email to Philip at Gmail, dot com and the password

test test again.

I'll sign up and we should jump into our code or not.

Yeah, OK.

If you don't see where you are in the code, you just click here, this arrow, the second one and you

should be in the register, right?

And you should see their credentials.

Then you will hover over these credentials, you'll see about getting on the user credentials user and

that's your user data.

So you have here, for example, access token display name is.

You don't have any any and name associated with this account.

Here is your email.

I have been provided email verified that you verified.

You can see a link and provide you basically any email into the input so that basically the email is

not verified yet.

And all these informations you have, you have here.

OK, but that's really not a concern of us, the other data we just need to have been to just have a

be sure that you have your email and the IDs here you kids called your ID.

As you can see down here.

All right, guys, I will show you what, what can happen when you will get error so everybody will

try to provide here.

Our producer incorrect data, so it's the email will be null and the pass will be no, no.

So Busselton lawsuit, this will for sure fail now.

I cannot even compile it.

So I just need to remove the email and password because are not using it.

So just for now, for testing purposes, I will leave here empty register and we'll get there.

No, no.

Let's save it.

Make the browser open the console so you can see what will happen and I will sign up.

OK, so you can see up there while I get to hear this error message from my console at our Firebase

error of administrated operation.

OK, so that's what will happen, will be on the register.

I will get better.

Is coming from the catch here.

OK, let's review the changes so we have here for sure.

Underscore email password and this should work for us before it gets here a semicolon in the end.

OK, I will finish the lecture here.

We have that two users now.

But as you see here, are there a couple of problems?

We don't have user username, double checking for a confirmation password, and overall we would like

to maybe provide a more detailed, maybe more data to the user.

How to handle it.

I'll be showing you in the next lecture.

See you there, guys.