Free Trial

Safari Books Online is a digital library providing on-demand subscription access to thousands of learning resources.

Share this Page URL

9 Managing WebLogic Server Security > WebLogic Server Security Basics - Pg. 426

Chapter 9: Managing WebLogic Server Security 397 Security providers OPSS offers several security providers that support various identity stores for authentication, including Oracle Internet Directory, Oracle Virtual Directory, Microsoft Active Directory, IBM Tivoli Directory, and Open LDAP. Security stores OPSS uses a single logical store for storing both policies and credentials, allowing it to support XML, LDAP, and database-based security stores without application code changes. You can start with an XML-based store and migrate to an LDAP store without any changes and without redeployment of your applications. WebLogic Server Security Basics Let's start the WebLogic Server security implementation by discussing the various WebLogic Server resources that the WebLogic Security Service protects. It's important to realize that there are two distinct categories of resources that you will be protecting. One set applies to the various entities that make up the administrative domain. For these, WebLogic Server provides a complete set of groups and policies. The second set of resources includes the ones you introduce when you deploy your application. While they are controlled with the same set of tools, they are quite distinct and it's easy to get confused unless you keep this distinction in mind. Following that, this section provides a quick introduction to how a security realm helps you manage security for a domain. You'll also learn about the default WebLogic security providers that help you manage various aspects of WebLogic security, such as authentication, authorization, and auditing.