We discussed a lot about password encoders and how security leverages them for violating the password.
So let's try to quickly recap what we discussed in this Section four.
At the very start of this section, we verified hotspring security, trying to validate the passwords
by default and in the cases of hasheem.
And we also discussed about the general terms, what is encoding encryption and hashing out, what's
the difference between them?
And finally decided that hacking is the most optimal way of handling and storing the passwords inside
your application and that database.
And also we looked at what is a password encoded interface, what kind of methods that we have to override
if we want to implement that.
And we saw there are two important methods inside it.
One is encode and other one is Matyas.
We also discussed about what the various passwords and codes which are provided by spring security by
default, and decided that secret password encoder and a script password encoders as the most powerful
password in Congress.
And any application can use them safely without any issues or daily discussions.
We also updated our application by implementing a secret password and and at the same time maintaining
user details in the database with the hash tag password that follows the script.
Algate and at the end of the section, we also discussed the importance of the crypto package that is
provided by spring security and what kind of features that it provides in terms of key generators,
encryption and decryption of that data.
So with this, we are done with the password encoder, which is the most important component in the
authentication flow of spring security.
If we have any questions, please feel free to post in the Q&A and I will see you in the next room.
Thank you.
By.