The best Course to Learn Spring Security 5 for Experienced Java Developers
阿新 • • 發佈:2018-12-29
If you are a Java Spring developer and working with Spring Security then you may be familiar with the "Learn Spring Security" course by Eugen Paraschiv of Baeldung.com. It is one of the most advanced and comprehensive courses on Spring Security and the best part of this course is that Eugen always keeps it up-to-date with new Spring Security release. Now that version Spring Security 5 is out - he has updated his course to use new features of Spring Security 5. Btw, there is some really cool new functionality coming in Spring Security 5 for the reactive programming model, and many other improvements and new features. But, the most important one is the release of OAuth2.
This means:
course to learn Spring security, you should use one which is focused on Spring Security 5 and Eugen has done a commendable job to update his course right in time.
Btw, he is not only updating existing lesson but also adding new modules, lessons and expanding the scope of the course to touch base some more advanced topics e.g. Security Architecture.
A lesson on Security Architecture is also coming
He is also adding a new chapter on Security Architecture, which is what most students have requested him from last year.
As per Eugen, the course material is very much focused on practical implementation, and he wants to keep that way.
But, he agrees that there are certainly a couple of architectural scenarios which he sees over and over again in his client engagements - that are core to implementing a real-world security system today.
One very common scenario is handling token verification in a microservice architecture, using OAuth.
Simply put, instead of having to verify the token in each microservice independently, the token is checked in the Gateway and gets propagated down.
That way, when a single request hits multiple services, the token isn't checked multiple times.
- No more picking spring-social modules to integrate with third-parties OAuth providers.
- No more limitations in the way the OAuth2 spec is implemented.