1 00:00:00,240 --> 00:00:05,860 In this video, let's try to recap what we have discussed in this Section three at the very starting 2 00:00:05,880 --> 00:00:12,510 of this section, we enhanced our application right from quoting one user in the application of properties 3 00:00:12,750 --> 00:00:20,190 into maintaining and adding multiple users through in-memory authentication and in-memory user details, 4 00:00:20,190 --> 00:00:27,930 manager posts that we looked how user contract and schema maintained by spring security by understanding 5 00:00:27,930 --> 00:00:32,150 all the important interfaces and classes revolving around it. 6 00:00:32,280 --> 00:00:39,180 The very first interface that we have looked at user details, which is the contract or blueprint of 7 00:00:39,390 --> 00:00:42,740 the user that brings security, wants to maintain. 8 00:00:43,140 --> 00:00:48,510 And we also looked at a sample implementation provided by spring security framework itself, which is 9 00:00:48,510 --> 00:00:49,010 user. 10 00:00:49,230 --> 00:00:55,950 After that, we also looked at the interface user details service, which is an interface where we can 11 00:00:55,950 --> 00:01:03,420 override and implement the logic on how to fetch the user details a bit from database relapser or any 12 00:01:03,420 --> 00:01:04,010 other place. 13 00:01:04,410 --> 00:01:12,180 And we also saw to handle scenarios like adding user deleting, updating user and changing passwords. 14 00:01:12,540 --> 00:01:15,230 We have an interface user details manager. 15 00:01:15,480 --> 00:01:21,540 Lastly, we also looked at the three implementations of user details manager provided by spring security, 16 00:01:21,540 --> 00:01:28,220 which are in memory user details, meningitidis, user details, manager and user details manager. 17 00:01:28,440 --> 00:01:36,000 So we went and looked into all these interfaces and classis what is a code present inside the framework? 18 00:01:36,120 --> 00:01:40,530 And we went into deep understanding database user details manager. 19 00:01:40,530 --> 00:01:48,130 Since this is the most famous, uncommon way of handling the authentication in any of the application. 20 00:01:48,420 --> 00:01:55,710 After that, we tried to do some hands on by creating a database in the database cloud for our application 21 00:01:55,710 --> 00:01:59,580 and integrating the database to our Zupanc application process. 22 00:01:59,610 --> 00:02:06,960 We also created certain users and we also implemented our own user detailed service and indicated our 23 00:02:06,960 --> 00:02:13,740 application to fetch the user details based upon the new tables and columns that were created to perform 24 00:02:13,740 --> 00:02:15,840 the authentication and authorization. 25 00:02:16,020 --> 00:02:22,110 For your reference, uploading the code that we have developed in this section to this, will you, 26 00:02:22,110 --> 00:02:27,900 where you can download at the Minuteman Project and you can input into our workspaces and you can see 27 00:02:28,110 --> 00:02:31,440 what I have done and you can treat it as a reference. 28 00:02:31,590 --> 00:02:36,770 And I request you to do some Hands-On based upon our discussion in this Section three. 29 00:02:36,990 --> 00:02:43,050 How also providing the scripts that I have been executing on the database side, for your reference, 30 00:02:43,320 --> 00:02:43,600 right. 31 00:02:43,620 --> 00:02:48,870 From creating a database, creating tables and inserting records into the database. 32 00:02:49,050 --> 00:02:53,310 So please download compare with what you have developed along with our discussion. 33 00:02:53,310 --> 00:02:59,670 And if you have any issues, you can always treat this as a reference for your project that you have 34 00:02:59,670 --> 00:03:01,650 been developing with me. 35 00:03:01,830 --> 00:03:06,610 And if you have any questions, please feel free to post your questions in the Q&A section. 36 00:03:06,810 --> 00:03:07,350 Thank you. 37 00:03:07,350 --> 00:03:08,910 And see you in the next review by.