1
00:00:00,430 --> 00:00:08,109
In the previous video, we have discussed in detail about what is encoding encryption and hashing and

2
00:00:08,770 --> 00:00:14,860
hashing is a clear winner that we should follow for any password management in our application.

3
00:00:15,550 --> 00:00:22,660
So this is a sample representation on hotspring security will be here if you try to use the hash like

4
00:00:23,140 --> 00:00:29,370
the very first action that performed by the user as soon as he entered his credentials and clicked login,

5
00:00:29,830 --> 00:00:31,600
you can convert the password.

6
00:00:31,600 --> 00:00:38,170
One, two, three, four, five by using a hashing algorithm either on the other side or in the back

7
00:00:38,170 --> 00:00:40,210
and say based upon your requirement.

8
00:00:40,660 --> 00:00:47,860
So once that was null, password is hashed, it will be into some encrypted value, which looks like

9
00:00:47,860 --> 00:00:49,780
this post that spring.

10
00:00:49,790 --> 00:00:57,370
Security will try to pull the details from the database by using the user name of the user and retrieve

11
00:00:57,460 --> 00:01:01,000
the already hash tag password of one, two, three, four, five.

12
00:01:01,300 --> 00:01:09,400
And here you can see the hash value that we generated based upon the value provided by user.

13
00:01:09,640 --> 00:01:14,290
And the hash that we maintain in the database today looks different.

14
00:01:14,530 --> 00:01:18,910
But they are the hash values of the same text, which is one, two, three, four, five.

15
00:01:19,120 --> 00:01:25,560
So in this scenario, the hash value, which is from the database and the hash that we calculate there

16
00:01:25,780 --> 00:01:26,830
is equal.

17
00:01:27,220 --> 00:01:32,530
So if it matches the Loganville, is that always the login will face?

18
00:01:32,800 --> 00:01:40,030
But you may ask how spring security will know what is a hashing mechanism that I have to use, what

19
00:01:40,030 --> 00:01:42,670
kind of hash that sprint security follows?

20
00:01:43,000 --> 00:01:45,640
And where does this match will happen?

21
00:01:45,850 --> 00:01:51,820
And where does this conversion of hashing will happen based upon the value received from the UI, from

22
00:01:51,820 --> 00:01:53,030
the postman.

23
00:01:53,380 --> 00:01:58,000
So for all such questions, password and quarter is the answer.

24
00:01:58,450 --> 00:02:05,400
So like we're discussing in the architecture of spring security, user details and Password and Corde

25
00:02:05,590 --> 00:02:10,400
are fully responsible for validating the credentials.

26
00:02:10,600 --> 00:02:14,640
So password and the retail spring security.

27
00:02:14,710 --> 00:02:19,940
OK, my password has been hashed are encrypted using this mechanism.

28
00:02:20,260 --> 00:02:28,490
You have to follow the same mechanism while matching the passwords and accordingly try to do the identification.

29
00:02:28,540 --> 00:02:35,200
So let's try to look in detail about password and for that in the next video, you have any questions?

30
00:02:35,200 --> 00:02:38,300
Please post in queue and I'll get you in the next week.

31
00:02:38,370 --> 00:02:38,790
Thank you.

32
00:02:38,800 --> 00:02:39,010
By.