In the last couple of videos, we have looked at the user detailed interface, which is a contract maintained
by the spring security whenever it tries to deal with the user details.
And at the same time, whenever we want to customize the user schema, our contract, our support requirement,
then we should always implement user details interface.
And at the same time, we also looked at the user data service interface, which have only a single
matter, which will load the user.
Details from the persistent layer of database are held up by using a user name.
But if we have scenarios where your application also has to handle creating, updating, deleting the
user details, then use a detailed service interface will not be enough in altered scenarios.
We should go ahead and implement user details manager interface, which internally extends user details,
service interface as well.
So in this video, let's try to see inside the framework of spring security about the user details manager
interface.
Now we are inside the user details manager interface present inside our spring framework with this package.
Now, as we discussed in the slide, user details manager, extending user details are ways.
That means whatever single method that we have inside user detailed service load user by user name will
also present in this interface.
And who are want to implement this user details manager has to provide a concrete implementation for
all these methods.
Like if I want to have a scenario of create an user, then we will call create user.
And as you can expect, the argument of this method is user details.
So what our input argument that you're sending to this create user update user, it has to follow the
schema provided by user details interface.
Similarly, in the case of updating the user details, we can update user and for deleting user from
your database or relapser.
We should override this method followed by if you have a scenario where you want to allow the user to
change password by themselves, then you can go this method and implement accepting the old password,
a new passport and eventually updating the database.
And lastly, we also have a simple matter, which is user.
Suppose you don't want to load the details of the user.
You just wanted to check if the user.
But I'm going to provide with the user name is present inside my database so far.
Altered scenarios.
You can always implement the method user exist in your custom class.
So this is about user details, manager and how to extend user details services and what type of methods
are available inside this interface.
So it's very clear the very first thing that interplaying security we have to understand is user details,
which holds the schema a blueprint of user.
And then we have user detail services which have only a single method where we can load the user details
by using it user name.
On top of that, we also how user details manager, which will allow you to manage user details like
creating, updating, deleting change password and user check.
So all such things are possible using user details.
Manage the next video.
Let's try and look.
What are the default implementations provided by spring security which extends this user details?
Maneesha, that means we have three famous default implementation of spring security where they ordered
all these methods by extending this user d'états manager to let's try to look into them in detail in
the next week.
Thank you.
By.