Thanks! And why securing repository, but not service layer? I mean, I might need db calls to check if user has permission for particular resource. If I perform several repository calls in service layer it will spam in numerous db calls in order to secure each repository check call. And another question - how to handle cases when I need to allow anonymous user to perform certain operation using secured method. For example I need to save new User using userRepo.save(), but it is secured.
Great Presentation. The original gradle version would not run in Intellij 14.12 due to jackson-databind.jar dependency's mismatch. see issue at github.com/rwinch/spring-security-4.1-and-beyond/issues/21 The netbeans 8.2 tested maven version of presentation branch is hosted -github.com/mingqin1/spring-security-4.1-and-beyond/tree/presentation . The maven converted codes serve the purpose of encourage of learning . All the credits go to Rob Winch, Joe Grandja