| Oracle® Database Advanced Security Administrator's Guid
e 10g Release 1 (10.1) Part Number B10772-01 |
|
|
View PDF |
This chapter describes how to use Enterprise Security Manager to administer Enterprise User Security in Oracle Databases. This chapter contains the following topics:
Enterprise Security Manager and Ent erprise Security Manager Console are the two main tools provided for administering Enterprise User Security.
a>Use Enterprise Security Manager to create and manage
Use Enterprise Security Manager Console to create, manage, and configure
These tools are introduced in Chapter 2, "Configuration and Administration To ols Overview" where you can find information about starting each tool and navigating its interface.
< p class="BP">In particular, refer to the following topics to get started using Enterprise User Security administration tools:| Tool | Introductory Topics |
|---|---|
|
Enterpri se Security Manager |
|
|
Enterprise Security Manager Console |
<
td class="Informal">
An identity management realm is a subtree of directory entries, all of which are governed by the s ame administrative policies. A realm Oracle Context is a subtree in a directory identity management realm that contains the data used by any installed Oracle product that uses the directory. Enterprise Security Manager is one such product. It lets you manage databas e and security-related information in an identity management realm.
This section describes how to use Enterprise Security Manager to administer directory identity management realm properties that pertain to Enterprise User S ecurity. It contains the following topics:
See Also:
|
Enterpris e User Security can only use an identity management realm supplied by Oracle Internet Directory 10g (9.0.4) o r later, which ships with Oracle Application Server 10g (9.0.4). You can manage Enterprise User Security dire ctory entries in a version 9.0.4 identity management realm by using Enterprise Security Manager for Oracle Database 10g.
Enterprise Security Manager displays all existing version 9.0.4 identity manage ment realms in its main application tree.
An identity management realm has a number of properties that can be viewed and managed by using Ent erprise Security Manager. These properties are described in Table 13-1.
| < a name="1010239"> Property | Description |
|---|---|
|
Attribu te for Login Name |
Name of the directory attribute used to store log
in names. By default, login names are stored in the |
|
Name of the directory attribute used to store Kerberos principal names. By default, Kerberos principal nam
es are stored in the | |
|
User Search Base |
Full distinguished name (DN) for the node at which enterprise users are stored in the directory. |
|
Group Search Base td> |
Full DN for the node at which user groups are stored for this identity m anagement realm in the directory. |
|
a>
Version Compatibility |
This property is no longer
used. However, you should ensure that it is not set to |
Setting these identity management realm attributes enables the database to locate Enterprise User Security entries.
Setting the default database-to-directory authentication type, enters a value for the LDAP_DIRECT
ORY_ACCESS initialization parameter. This parameter is set on individual databases when they are registered in Oracle Internet
Directory.
An identity management realm contains administrative grou ps that have varying levels of privileges. The administrative groups for an identity management realm, which pertain to Enterprise Us er Security, are defined in Table 13-2. For more information about these groups, see "Administrative Groups".
| Administrative Group< /font> | Definition |
|---|---|
|
Oracle Database Registration Administrators (OracleDBCrea tors) |
Registers new databases in the realm. |
|
Oracle Database Security Administrators (OracleDBSecurityAdmins) |
Has all privileges on the OracleDBSecurity directory subtree. Creates, modifies, and can read all Enterprise User Security directory objects. |
|
(OracleContextAdmins) |
<
/a>
Has full access to all groups and entries within its associated realm. |
|
(OracleUserSecurityAdmins) |
Has relevant permissions nece ssary to administer security aspects for enterprise users in the directory. For example, OracleUserSecurityAdmins can modify user pas swords. |
Enterprise Security Manager manages one directory server at a time, iden tified at the top of the main application tree. It lets you manage enterprise users and data that is relevant to Enterprise User Secu rity in the identity management.
This section describes how to use Enterprise Security Mana ger to administer enterprise users. It contains the following topics:
Use Enterprise Security Manager to create users in the directory.
Bef ore creating new enterprise users, you must define the user search base in the directory. See "Setting Login Name, Kerberos Principal Name, User Search Base, and Group Search Base Identity Management Realm Attributes"
Text description of the illustration esmconso.gif
You can set and maintain enterprise user passwords in the Basic Info rmation region of the Enterprise Security Manager Console Edit User window (Figure 13-2).
Text description of the illustration edituser.gif
The enterprise user password is used for:
A list of all users that match your search cri teria displays.
When you create a new enterprise user, you can grant any previously configur ed enterprise roles to the new user.
| See Also:
"Administering Enterprise Roles"< a href="asoadmeu.htm#1008211"> |
The Add Enterprise Roles window a ppears (Figure 13-3):
Text description of the illustration esm0009.gif
Enterprise Security Manager lets you browse the directory for all users currently stored there in two ways--by using Enterprise Secur ity Manager Console, or by using the All Users tab in the main application window.
A list of all users that match your searc h criteria displays. You can browse through the displayed users and select one to Edit, Delete, or Assign Privileges. If you need to create a new user, click Create.
Text description of the illustration esm0011.gif
Note that you ca n also browse enterprise users in the directory by selecting realm_name > User, by Search Base > Users in the left navigation pane of the main application window.
An identity management realm contains an enterprise domain called OracleDef
aultDomain. The OracleDefaultDomain is part of the realm when it is first created in the directory. When a new da
tabase is registered into a realm, it automatically becomes a member of the OracleDefaultDomain in that realm. You can c
reate and remove your own enterprise domains but you must not remove the OracleDefaultDomain from a realm.
This section describes how to use Enterprise Security Manager to administer enterprise domains in the di rectory. It contains the following topics:
If you do not want to use the OracleDefaultDomain, then you can create a new enterprise do
main in your identity management realm.
The Create Enterprise Domain window appears (Figure 13-5):
Text description of the illustration esm0023.gif
Use the navigation tree of the main Enterprise Security Manager window to select a spec ific enterprise domain. You can then use the Databases tab to manage database membership of an enterprise domain in a realm (Figure 13-6):
Text description of the illustration esm00 25.gif
Text description of the illustration esm0026.gif
Use the Databases tabbed window (Figure 13-6) to manage database secu rity options applicable to all databases that are members of the enterprise domain.
Databas e security options are summarized by Table 13-4:
An Enterprise Domain Administrator is a directory user with privileges to modify the content of that domain. You can use the Administrators tabbed window to manage Ente rprise Domain Administrators when an enterprise domain is selected under an realm in the main application tree.
Data base schema mappings, also referred to as user schema mappings) let databases that are registered in the directory accept connections from users without requiring any dedicat ed database schemas for them. For example , when local user Scott connects to a database, a database schema called Scott must exist--for that logon to be successful. This can be difficult to maintain if there are thousands of users and perhaps hundreds of databases in a very large enterprise.
Users that are defined in an LDAP-compliant directory do not require dedicated schemas on every Oracle9
A database can use a schema mapping to share one database schema between multiple directory users. The schema mapping is a pair of values: the base in th e directory at which users exist, and the name of the database schema they will use.
You ca n use the Database Schema Mappings tabbed window to manage database schema mappings--when a database is selected under a realm in the main application tree or when a domain is selected. If a domain is selected, these mappings apply to all databases that are members of the enterprise domain. Therefore, each database in the enterprise domain must have a schema of the same name used in the mapping f or that mapping to be effective on that database. This window contains a list of database schema names, directory DNs, and mapping ty pes (Figure 13-8):
Text description of the illustration esm0020.gif
The Add Database Schema Mappings window appears (Figure& nbsp;13-9). Use this window to locate and select a base in the directory and pair it with a database schema name, to make a datab ase schema mapping. There are three components to the window: there is a directory search tree from which to select the user's DN or the base of users, the option to choose either subtree-level or entry-level mapping, and a field in which to enter a schema name.
Text description of the illustration esm0021.gif
There are three requirements for a database to accept a connection from a password-authe nticated user:
Text description of the illustration esmpwacc.gif
|
Note:
|
A Database Administrator i s a directory user that has privileges to modify the database and its subtree in the realm. Database Administrators may be managed by using the Administrators tabbed window when a database is selected under a realm in the main application tree.
An enterprise domain within an identity m anagement realm can contain multiple enterprise roles. An enterprise role is a set of Oracle role-based authorizations across one or more databases in an enterprise domain.
This section describes how to use Enterprise Security Manager to administer enterprise roles in the directory. It contains the follow ing topics:
You can cre ate an enterprise role in an enterprise domain either from the Operations menu on the Enterprise Security Manager main window (Figure 13-8), or by right-clicking an enterprise domain in the main application tree. In either cas e, the Create Enterprise Role window appears (Figure 13-11):
Text description of the illustration esm0030.gif
Use the Database Global Roles tabbed window (Figure 13-12) of the Enterprise Security Manager main window to manage d atabase global role membership in an enterprise role. This window lists the names of each global role that belongs to the enterprise role, along with the name of the database on which that global role exi sts.
Text description of the illustration esm0031.gif
When populating an enterprise role with different database roles it is only possible to reference roles on
databases that are configured to be global roles on those databases. A global role on a database is identical
to a normal role, except that the Database Administrator has defined i
t to be authorized only through the directory. (Global roles are created with the syntax, CREATE ROLE <role_name> IDENTIF
IED GLOBALLY ' ';) A Database Administrator cannot locally grant and revoke global roles to users of the database.
Note that the name of the database appears in the Service field by default. You can use this name to connect to the d
atabase if your Oracle home has LDAP enabled as its Oracle Net naming method, or if this name appears as a TNS alias in your local Or
acle Net configuration. Otherwise, you can overwrite the content of the Service field with any other TNS alias configured for that da
tabase, or by a connect string in the format <host>:<port>:<oracle sid>. For example, cartman:15
21:broncos.
Text description of the illustration esm0034.gif p>
You can grant an enterprise role to users in two ways: you can select a user and add a role (see "Defining an Initial Enterprise Role Assignment"), or you can select a role and add a user. When you grant an enterprise role to a user, it includes all datab ase global roles contained within that enterprise role. Use the Users tabbed window.
T ext description of the illustration esmadusr.gif