1 Introduction and Roadmap

Document Scope

This document explains how to configure WebLogic Server security, including settings for security realms, providers, identity and trust, SSL, and Compatibility security. See Related Information, for a description of other WebLogic security documentation.

Document Audience

This document is intended for the following audiences:

• Application Architects—Architects who, in addition to setting security goals and designing the overall security architecture for their organizations, evaluate WebLogic Server security features and determine how to best implement them. Application Architects have in-depth knowledge of Java programming, Java security, and network security, as well as knowledge of security systems and leading-edge, security technologies and tools.

• Security Developers—Developers who define the system architecture and infrastructure for security products that integrate with WebLogic Server and who develop custom security providers for use with WebLogic Server. They work with Application Architects to ensure that the security architecture is implemented according to design and that no security holes are introduced, and work with Server Administrators to ensure that security is properly configured. Security Developers have a solid understanding of security concepts, including authentication, authorization, auditing (AAA), in-depth knowledge of Java (including Java Management eXtensions (JMX)), and working knowledge of WebLogic Server and security provider functionality.

• Application Developers—Java programmers who focus on developing client applications, adding security to Web applications and Enterprise JavaBeans (EJBs), and working with other engineering, quality assurance (QA), and database teams to implement security features. Application Developers have in-depth/working knowledge of Java (including J2EE components such as servlets/JSPs and JSEE) and Java security.

• Server Administrators—Administrators work closely with Application Architects to design a security scheme for the server and the applications running on the server; to identify potential security risks; and to propose configurations that prevent security problems. Related responsibilities may include maintaining critical production systems; configuring and managing security realms, implementing authentication and authorization schemes for server and application resources; upgrading security features; and maintaining security provider databases. Server Administrators have in-depth knowledge of the Java security architecture, including Web services, Web application and EJB security, Public Key security, SSL, and Security Assertion Markup Language (SAML).

• Application Administrators—Administrators who work with Server Administrators to implement and maintain security configurations and authentication and authorization schemes, and to set up and maintain access to deployed application resources in defined security realms. Application Administrators have general knowledge of security concepts and the Java Security architecture. They understand Java, XML, deployment descriptors, and can identify security events in server and audit logs.

Guide to This Document

This document is organized as follows:

• This chapter describes the audience, organization, and related information for this guide.

• Chapter 2, "Overview of Security Management," describes the default security configuration in WebLogic Server; lists the configuration steps for security, and describes Compatibility security.

• Chapter 3, "Customizing the Default Security Configuration," explains when to customize the default security configuration, the configuration requirements for a new security realm, and how to set a security realm as the default security realm.

• Chapter 4, "Configuring WebLogic Security Providers," describes the available configuration options for the security providers supplied by WebLogic Server and how to configure a custom security provider.

• Chapter 5, "Configuring Authentication Providers," describes the Authentication providers supplied by WebLogic Server, including information about how to configure them.

• Chapter 6, "Configuring Single Sign-On with Microsoft Clients," describes how to configure authentication between a WebLogic domain and .NET Web service clients or browser clients (for example, Internet Explorer) in a Microsoft domain, using Windows authentication based on the Simple and Protected Negotiate (SPNEGO) mechanism.

• Chapter 7, "Configuring Single Sign-On with Web Browsers and HTTP Clients," describes how to configure authentication between a WebLogic domain and Web browsers or other HTTP clients, using authentication based on the Security Assertion Markup Language (SAML).

• Chapter 8, "Migrating Security Data," provides information about exporting and importing security data between security realms and security providers.

• Chapter 9, "Managing the Embedded LDAP Server," describes the management tasks associated with the embedded LDAP server used by the WebLogic security providers.

• Chapter 10, "Managing the RDBMS Security Store," describes the steps required to configure the RDBMS security store, which enables you to store the security data managed by several security providers in an external RDBMS system rather than in the embedded LDAP server. The use of the RDBMS security store is required for SAML 2.0 services when configured on multiple servers in a domain, such as in a cluster.

• Chapter 11, "Configuring Identity and Trust," describes how to configure identity and trust for WebLogic Server.

• Chapter 12, "Configuring SSL," describes how to configure SSL for WebLogic Server.

• Chapter 13, "Configuring Security for a WebLogic Domain," describes how to set security configuration options for a WebLogic domain.

• Chapter 14, "Using Compatibility Security," describes how to use Compatibility security, a security configuration mode designed for backwards compatibility with security realms developed under WebLogic Server 6.x.

• Chapter 15, "Security Configuration MBeans," describes which WebLogic Security MBeans and MBean attributes are dynamic (can be changed without restarting the server) and which are non-dynamic (changes require a server restart).

Related Information

The following Oracle Oracle Fusion Middleware documents contain information that is relevant to the WebLogic Security Service:

• Understanding Security for Oracle WebLogic Server—Summarizes the features of the WebLogic Security Service, including an overview of its architecture and capabilities. It is the starting point for understanding WebLogic security.

• Developing Security Providers for Oracle WebLogic Server—Provides security vendors and application developers with the information needed to develop custom security providers that can be used with WebLogic Server.

• Securing a Production Environment for Oracle WebLogic Server—Highlights essential security measures for you to consider before you deploy WebLogic Server in a production environment.

• Securing Resources Using Roles and Policies for Oracle WebLogic Server—Introduces the various types of WebLogic resources, and provides information about how to secure these resources using WebLogic Server. This document focuses primarily on securing URL (Web) and Enterprise JavaBean (EJB) resources.

• Programming Security for Oracle WebLogic Server—Describes how to develop secure Web applications.

• Securing WebLogic Web Services for Oracle WebLogic Server—Describes how to develop and configure secure Web services.

• Oracle WebLogic Server Administration Console Help—Many security configuration tasks can be performed using the WebLogic Administration Console. The console's online help describes configuration procedures and provides a reference for configurable attributes.

• Upgrade Guide for Oracle WebLogic Server—Provides procedures and other information you need to upgrade from earlier versions of WebLogic Server to this release. It also provides information about moving applications from an earlier version of WebLogic Server to this release. For specific information on upgrading WebLogic Server security, see "Upgrading a Security Provider" in Upgrade Guide for Oracle WebLogic Server.

• Oracle WebLogic Server API Reference—Provides reference documentation for the WebLogic security packages that are provided with and supported by this release of WebLogic Server.

Security Samples and Tutorials

In addition to the documents listed in Related Information, Oracle provides a variety of code samples for developers, some packaged with WebLogic Server and others available at the Oracle Technology Network (OTN) at https://www.samplecode.oracle.com/.

New and Changed Security Features

For a comprehensive listing of the new WebLogic Server features introduced in this release, see What's New in Oracle WebLogic Server.