Book Image

Spring Security Essentials

By : Nanda Nachimuthu
Book Image

Spring Security Essentials

By: Nanda Nachimuthu

Overview of this book

<p>Spring Security is a framework that focuses on providing both authentication and authorization to Java applications. Like all Spring projects, the real power of Spring Security is how easily it can be extended to meet custom requirements. The popularity of the Spring framework is increasing and the security package of Spring addresses vast mechanisms of Security in a rich way. Due to an increasing number of applications for various business needs, the integration of multiple applications is becoming inevitable. The standard security procedures available across multiple implementations in Spring will protect vulnerable applications that are open to larger public and private audiences.</p> <p>Spring Security Essentials focuses on the need to master the security layer, which is an area not often explored by a Spring developer.</p> <p>At the beginning, we’ll introduce various industry standard security mechanisms and the practical ways to integrate with them. We will also teach you about some up-to-date use cases such as building a security layer for RESTful web services and applications.</p> <p>The IDEs used and security servers involved are briefly explained, including the steps to install them. Many sample projects are also provided to help you practice your newly developed skills. Step-by-step instructions will help you master the security layer integration with the Server, then implement the experience gained from this book in your own real-time application.</p>
Table of Contents (17 chapters)
Spring Security Essentials
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
Index

AOP terminologies


The AOP terminologies are as follows:

  • Aspect: This is a module or package that has a set of APIs that are used to address the cross-cutting requirements. For example, an exception module can be treated as an AOP aspect for Exception Handling.

  • Join point: The plugging point to introduce the aspect in the application is called join point. This is where the AOP code will start its activities.

  • Advice: This is where the actual actions such as Logging or Exception are handled from the Aspect code, which is not a part of the application code. The Action can be initiated before or after the application method execution. Advice is of four types, as follows:

    • Around advice: This will have the custom code that is to be executed before and after the method invocation. We can decide on the proceedings to the join point, or we can return some values, or we can decide on throwing some exceptions using Around advice.

    • Before advice: Before executing join points, this advice will be called...