Applications and Navigation - Beginning Oracle Application Express 4.2 - page 84

5. Select No for Copy Shared Components from Another Applica-
tion , and click Next .

Application Attributes

The next step in the wizard allows you to set some of the application-level attributes
such as the type of authentication to use, whether to use tabs, and globalization attrib-
utes including where to derive the primary language, date formats, and so on. Let's
look at each of these individually so you can gain a full understanding of the ramifica-
tions of each.

Selecting an Authentication Method

With every application, you need to make a choice about authentication, even if that
choice is no authentication at all. This topic is discussed further in Chapter 9 . By de-
fault, the APEX Create Application Wizard provides three options for authentication:

• Application Express : Users and passwords are local to the APEX work-

space. These users are managed in the same way the developer accounts are
managed inside the APEX workspace, and users only work inside the cur-
rent workspace.

• No Authentication : This is like a public web site. Users aren't prompted

for any type of authentication. This is useful for informational applications
where the question “Who are you?” isn't important.

• Database Account : This option uses the Oracle Database schema user-

names and passwords for credentials. Some organizations use this type of
database-driven authentication to keep track of users. The application still
executes as the chosen “parse as” schema, not as the individual user in the
database.

For simplicity, the default is to use the Application Express authentication scheme.
This is the one setting that provides login security; by default, the developer writing the
application can log in without any additional work.