스프링 시큐리티

I have only seen the API and architecture part, but it is a very good lecture. While studying JSP and Spring, I wanted to cover security and authorization in more detail. I searched the Internet, but I am still a beginner. Haha. The best part is that the lecture is very friendly. I can feel the sincerity in the materials provided, and the concepts are repeatedly explained so that even a beginner like me can understand. At first, there were so many concepts that it was too difficult, and I did not understand the debugging. But if you take notes diligently and follow along, you will now be able to see the overall flow. Thank you for making a good lecture.

I am a 4th year computer science student. In the case of Spring Security, if you search on Google, you will find a lot of information, and it is also a good idea to refer to the official reference on spring.io. However, in the case of security, the process of reorganizing scattered information is very difficult. Even if you search on Google without knowing anything, it only tells you how to set up SecurityConfig, and it does not explain in detail why it is used, so if you apply it to a personal project, you will encounter numerous errors. In my subjective opinion, if you do not know anything about security, I am sure that purchasing this lecture is much cheaper than the cost of searching and finding it yourself. If you are taking the lecture, it seems better to skip Chapters 1 and 2 at first and go straight to the practical training. If you are doing the practical training and you get stuck for some reason, you can understand it better and internalize it faster by looking at the detailed API explanation in Chapters 1 and 2. For example, when I only heard about Authentication Flow in theory, it was quite difficult, but when I applied it to my project in Chapter 3 of the practical training and listened to it again, the flow chart caught my eye right away. The PPT is also well organized by each step, so it is a material that I can carry with me for the rest of my life. I unconditionally recommend it to those who, like me, have simply sent password values directly to the DB without encryption in past projects, or made it so that all members who sign up can delete posts written by others, or simply made projects as a patchwork.

I've been so absorbed in the lecture that I haven't been able to get out for weeks. The materials you provide are amazing, and I can feel the depth of knowledge you share just by looking at the answers you give on the Q&A board. I think I should listen to it again quickly after finishing the lecture. I'm glad I found this gem of a lecture. I'm looking forward to the next lecture. Thank you for making such a great lecture. ^___^

I dare say that this is a truly rare Spring Security course, both domestically and internationally. I am listening to all three lectures by instructor Jeong Su-won, and I am amazed by the unique teaching pattern of instructor Jeong Su-won, such as the lecture content, preparation of materials, digging into the internal structure through debugging, and analyzing the entire architecture. Wow, digging into security like this... I think developers who have developed security will also be amazed by this lecture. As you know, Spring Security has a large learning curve, so it is not easy for intermediate developers to deeply understand the internal structure and flow, but this lecture provides sufficient technical foundation knowledge for beginners to intermediate developers and above. It explains in detail and easily so that difficult security does not feel like being possessed by magic, by combining appropriate theories and appropriate practices. In particular, the part where the structure and flow of Spring Security are explained in detail through well-prepared PPT diagrams and diagrams, and this is proven through debugging with code, is the highlight of this lecture and seems to be the instructor's know-how. I am also learning one by one by keeping an eye on this method of progress. Before taking this lecture, I only knew how to follow security, but after taking this lecture, I was able to acquire the ability to freely expand and customize functions according to the situation as well as the basic functions of security such as API, filter structure, authentication/authorization internal flow, and dynamic authorization control method. I would like to evaluate this lecture as an incredible level. I think it provides quality and information that can be counted among the lectures on Inferun. In fact, since security lectures are not a technology that anyone can teach if they want to, I think this lecture is even more valuable. After listening to it all, I realized how difficult and hard it would have been if I had tried to acquire this much knowledge on my own. When I search for security on Google, I see that the instructor's lecture contents are searched a lot, so I am really grateful that you have lowered the barrier to entry by spreading the high barrier to entry security knowledge to many developers. There was a problem where the explanation content and the provided GitHub source were not partially synchronized during the lecture, but fortunately, the instructor organized the branch names of the sources that were mapped to the lecture in Excel, so it was much easier to follow. There were some differences between the lecture content and the actual practice, but there was no difficulty in understanding the overall content. Still, I hope that you will look into these small parts more carefully in the next lecture. Now, I am looking forward to and anticipating Instructor Jeong Su-won's next lecture. Through knowledge sharing by developers like you, our junior developers will experience minimal trial and error. I will sincerely support the instructor's knowledge sharing activities in the future. Thank you.

The PPT is also very long and the lecture volume is also very high. The API is explained one by one by method, It is a lecture that helps a lot in understanding what Spring Security is, how it works, and why it is done this way, not just learning how to use it. You can also go to Git and get the source code. The disappointing thing is that even if you want to follow the code writing for each lecture step, Git only has the finished version, and the lecture does not show you all the functions implemented in the lecture in detail, and Git also has quite a few refactored and updated codes that are different from the lecture content, so it is confusing or you have to adjust it yourself, which is more tiring than you think. Except for those parts, I am satisfied and plan to take the lecture again for the second time to improve my skills.