Book Image

Securing WebLogic Server 12c

Book Image

Securing WebLogic Server 12c

Overview of this book

Security is a must in modern Enterprise architecture, and WebLogic implements a very complete and complex architecture for configuration and implementation, and we need to deeply know in technologies, terminology and how the security process works between all actors. Transparent security of your applications and Weblogic infrastructure need a good knowledge of the issues you can incur in this long and error prone configuration process. "Securing WebLogic Server 12c" will simplify a complex world like WebLogic Security, helping the reader to implement and configure. It's the only fast guide that will let you develop and deploy in a production system with best practices both from the development world and the operation world. This book will try to make a clear picture of Java EE Security with clean and simple step-by-step examples that will guide the reader to security implementation and configuration From the concepts of Java EE Security to the development of secure application, from the configuration of a realm to the setup of Kerberos Single Sign on, every concept is expressed in simple terms and surrounded by examples and pictures. Finally, also a way to develop WebLogic Security Providers with Maven, so that you can add the security part of your infrastructure to your enterprise best practices.
Table of Contents (12 chapters)

The Maven project


There is no WebLogic MBeanMaker plugin in our application and also the existing tool is not really Maven friendly.

Tip

WebLogic MBeanMaker

This is a command-line utility that generates all the files you need to form an MBean type, from partial Java classes to contract interfaces and some custom files used by WebLogic itself to introspect the MBean once it is deployed in JAR inside the system class loader.

What we will do is an integration of the existing technologies into Maven using the maven-antrun-plugin plugin as a bridge between these two worlds. These technologies are so invasive that we will have to disable some standard and common Maven plugins such as maven-jar-plugin and maven-install-plugin. In a sense, the work of the compile plugin will be done by this piece of ancient BEA technology.

But all of this makes sense if we want to have a piece of software that can be integrated into modern build systems, and if we want to have a good development environment where we...