Now, let's try to recap what we have discussed in this section.
We started this section with the discussion around authentication provided what is its role in the spring
security architecture and what are the scenarios that we need to go for an option of customizing this
authentication provider so that we can skip off adhering, heading to the user details and user details
of these user details.
Manager contact provided basically security.
We also looked at the definitions of authentication for the authentication manager and the methods inside
them and observed that authentication provider has two methods authenticate and supports, whereas authentication
manager has only one method, which is authenticate.
The difference between authentication provider and authentication manager is only supports method was
that we also discussed about the important interface, which is authentication followed by principle
and how they are similar to user details and also looked at how the user details will become with the
authentication object in the scenarios where we are using the default authentication provider, which
is the authentication provider from the spring security framework.
After that, we also looked into the provider manager and the authentication provider, which are default
implementations of authentication manager and authentication provider.
And so it's been security and we saw like how provider manager handles all the providers configured
inside my application.
How would we look each provider by provider and how it performs authentication authenticate method in
all the providers.
Finally, we enhanced our application to have a custom authentication provider and perform authentication
using it without any issues.
With that, we are concluding the authentication provider concept.
If you have any questions, please post in the comments section.
Thank you.
And Mike.