In the last few videos, we have made complete changes on the back and not to generate the beauty tokens
and we are also sending the generator JWT token inside the response as a header value with the name
of.
So now in this video, let's try to make some changes on the client application side as well to capture
that value.
And at the same time, for all future requests that this application is going to make for successful
logging.
And we have to make sure that we are passing the same gwg token inside the request to the backend so
the backend can validate every time we pass a request to prove our authentication and authorization.
So I'm at the logging company in tortillas.
Yeah, this is the place where the login of the user will happen by communicating to the backend.
Once I get the response from the back end, what I can do is can populate the Thracian JWT token on
the order of the response and put it into the station storage with the value alteration.
So now my operation value is inside the shared storage, my browser.
But in order to send the same value every time I'm making a request to the back and I have to make a
change inside the interceptor file that we have written for the CSR of tokens before that, since we
have removed all the CSR related stuff on the backend, we can remove on the front end, also not storing
that value no more.
Now I'll go to the interceptor file.
I'm going to remove the CSR of related port and add a code which will add our authorization JWT token
every time to the back end when a request is happening.
So here you can see I'm trying to get that value from the storage.
If it is not null, I'm sending in the request at the with the value alteration and it's a token value.
So this will make sure that I'm sending my same JWT token every time to that back.
So now let's try to start the service both on the front end and the back end and try to test how this
JWT tokens are working in the next room.
Thank you.
And see you in the next lecture by.