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)

SPNEGO Identity asserter configuration


To find SPNEGO Identity Assertion, go to the Admin Console and select Security Realms | myrealm | Providers.

Click on the Lock & Edit button to lock and edit your domain, proceed to the New button (naming your provider with a personal reference), and select the Negotiate Identity Assertion provider from the list and click on Ok. Reorder the provider sequence on top after LDAP is configured (see Chapter 2, WebLogic Security Realm). After all these modifications, restart all the nodes of your WebLogic Server, along with the Admin Console, to make your changes effective.

Now your WebLogic Server is able to accept Kerberos tokens in an HTTP connection, and it can establish a trusted relationship with your client when a Service Principal Name is called and the security is enabled in your Java application (refer to Chapter 3, Java EE Security With WebLogic, of this book to secure your path).

In the following diagram you can see an authentication schematic...