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)

Using Identity Assertion


Typically to support an SSO process, you need to have a LoginModule object and an Identity Assertion provider. With these objects, you can exploit tokens stored by the operating system to do the HTTP authorization process without entering username and password and gain access to your secure resources.

The LoginModule objects trust that the user has obtained the token by providing the username and password to another authority.

Your token can pass from client to server in different ways such as HTTP headers, cookies, SSL certificates, or other custom mechanisms. The Identity Assertion needs to grab this token and extract the security information to allow access to the secured context paths.

We will be using the SPNEGO Identity Asserter provider in Chapter 5, Integrating with Kerberos SPNEGO Identity Assertion to configure the SSO integration in an Active Directory context.