As a result, when KMOURGOS connects through the application server, he is
permitted to access, via the web, all tables and privileges granted to him via roles, except for the
order management functions. Because of the business rules in place at his company, all access to
the order management applications must be done via a direct connection to the database. Roles
are discussed in detail in the section titled ???Assigning and Maintaining Roles??? later in this chapter.
Client-Side Authentication
Client-side authentication is one way to authenticate users in a multitier environment, but Oracle
strongly discourages this method unless all clients are on a secure network, inside a firewall, with
no connections allowed to the database from outside the firewall. In addition, users should not
have any administrative rights on any workstation that can connect to the database.
If an Oracle user is created with the IDENTIFIED EXTERNALLY attribute, and the initialization
parameter REMOTE_OS_AUTHENT is set to TRUE, then an attacker can easily authenticate himself
on the workstation with a local user account that matches the Oracle user account, and as a result
gain access to the database.
As a result, it is strongly recommended that the REMOTE_OS_AUTHENT parameter be set to
FALSE. The database will have to be stopped and restarted for this change to take effect.
NOTE
As of Oracle Database 11g, the parameter REMOTE_OS_AUTHENT
is deprecated.
Pages:
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484