Skip Headers

Oracle® Application Development Framework Developer's Guide 10g Release 3 (10.1.3) B25386-01 |
| Home | Solution Area | Contents | Index

Previous | Next |

# 18.1 Introduction to Security in Oracle ADF Web Applications

Web application security can be provided by Oracle ADF Security. The Oracle ADF Security implementation is built upon a pluggable architecture that implements the Oracle Application Server Java Authentication and Authorizatio n (JAAS) Provider for authentication and authorization:

- Authentication provides a way to determine who the current user is. Oracle ADF Security can authenticate users against data within various resource providers.

- Authorization provides a way to restrict access to the application or parts of the application (called resources) based on the user attempting to access the resource. Oracle ADF Security allows you to set authorization on ADF Model layer objects.

First, you must configure the application to use a resource provider. The user data by which the login and passwords are authenticated is stored within a resource provider, such as a database or LDAP director. By editing the `jazn.xml` file, you choose an identity management provider for the OracleAS JAAS Provider. Read the following section to understand editing the `jazn.xml` file:

- Section 18.2, "Specifying the JAZN Resource Provider"

Then, you can configure the application's container to use Oracle ADF Security. This will allow you to use Oracle ADF Security for authentication and authorization. Alternatively, you can bypass Oracle ADF Security and use container-managed security. Read the following section to understand configuring the J2EE security.

Read the following sections to understand how to configure authentication and create login and logout pages:

- Section 18.3.1, "How to Enable Oracle ADF Authentication"

- Section 18.3.3, "How to Enable J2EE Container-Managed Authentication"

- Section 18.4, "Creating a Login Page"

- Section 18.5, "Creating a Logout Page"

When you want to assign resources to particular users, you can work with Oracle ADF Model layer to enable authorization. If you choose not to use ADF authorization, you can still work with ADF authentication. Alternatively, you can integrate standard J2EE authorization with the Oracle ADF Model layer to restrict resources. Read the following section to understand how to integrate Oracle ADF Model with programmatic authorization. Read the following sections to understand how to work with authorization:

- Section 18.6, "Implementing Authorization Using Oracle ADF Security"

- Section 18.7, "Implementing Authorization Programmatically"

Note: When you want to understand the security features of OC4J, see the Oracle Containers for J2EE Security Guide in the Oracle Application Server documentation library. For example, the "Standard Security Concepts" chapter provides a useful overview of the JAAS security model.