6 Configuring Rule Sets

About Creating Rules

You can create rules during the rule set creation process, or independently of it. You can associate the rule set with one or more additional rules.

If you create a new rule during the rule set creation process, the rule is automatically added to the current rule set. You also can add existing rules to the rule set. Alternatively, you can omit adding rules to the rule set and use it as a template for rule sets you may want to create in the future.

You can add as many rules that you want to a rule set, but for better design and performance, you should keep the rule sets simple. See"Guidelines for Designing Rule Sets" for additional advice.

The rule set evaluation depends on the evaluation of its rules using the Evaluation Options (All True or Any True). If a rule set is disabled, Oracle Database Vault evaluates the rule set to true without evaluating its rules.

See "How Rule Sets Work" for information on how rules are evaluated, how to nest rules, and how to create rules that exclude a particular user, such as a privileged user.

Default Rules

You can find a full list of rules by querying the DVSYS.DBA_DV_RULE data dictionary view.

Table 6-1 lists the default Oracle Database rules.

Creating a New Rule

You can create a new rule in Enterprise Manager Cloud Control.

To create and add a rule to a rule set:

1. From Cloud Control, log into Oracle Database Vault Administrator as a user who has been granted the DV_OWNER or DV_ADMIN role.

   "Logging into Oracle Database Vault" explains how to log in.

2. In the Administration page, under Database Vault Components, click Rules.

3. Click the Create button.

4. In the Create Rule page, enter the following settings:

   • Name: Enter a name for the rule. Use up to 90 characters in mixed-case.

     Oracle suggests that you start the name with a verb and complete the name with the purpose of the rule. For example:

     Prevent non-admin access to SQL*Plus
     

     Because rules do not have a Description field, make the name explicit but be sure to not exceed over 90 characters.

   • Rule Expression: Enter a PL/SQL expression that fits the following requirements:

     • It is valid in a SQL WHERE clause.

     • It can be a freestanding and valid PL/SQL Boolean expression such as the following:

       TO_CHAR(SYSDATE,'HH24') = '12'
       

     • It must evaluate to a Boolean (TRUE or FALSE) value.

     • It must be no more than 1024 characters long.

     • It can contain existing and compiled PL/SQL functions from the current database instance. Ensure that these are fully qualified functions (such as schema. function_name). Do not include any other form of SQL statements.

       Be aware that you cannot use invoker's rights procedures with rule expressions. Doing so will cause the rule evaluation to fail unexpectedly. Only use definer's rights procedures with rule expressions.

       If you want to use application package functions or standalone functions, you must grant the DVSYS account the EXECUTE privilege on the function. Doing so reduces the chances of errors when you add new rules.

     • Ensure that the rule works. You can test the syntax by running the following statement in SQL*Plus:

       SELECT rule_expression FROM DUAL;
       

       For example, suppose you have created the following the rule expression:

       SYS_CONTEXT('USERENV','SESSION_USER') != 'TSMITH'
       

       You could test this expression as follows:

       SELECT SYS_CONTEXT('USERENV','SESSION_USER') FROM DUAL;
       

       For the Boolean example listed earlier, you would enter the following:

       SELECT TO_CHAR(SYSDATE,'HH24')FROM DUAL;
       

     See the following sections for functions that you can use in the rule set expression:

     • "Oracle Database Vault PL/SQL Rule Set Functions"

     • "DBMS_MACADM Rule Set Procedures"

     • Chapter 19, "Oracle Database Vault Utility APIs"

     For additional examples of expressions, see the rule defined in the rule sets provided with Oracle Database Vault. "Default Rule Sets" lists these rule sets.

5. Click OK.

Adding Existing Rules to a Rule Set

After you have created one or more rules, you can use Enterprise Manager Cloud Control to add to a rule set.

To add existing rules to a rule set:

1. From Cloud Control, log into Oracle Database Vault Administrator as a user who has been granted the DV_OWNER or DV_ADMIN role.

   "Logging into Oracle Database Vault" explains how to log in.

2. In the Administration page, under Database Vault Components, click Rule Sets.

3. Select the rule set to which you want to add an existing rule, and then click Edit.

4. Click Next until you reach the Rules Associated with Rule Sets page.

5. Click Add Existing Rule to display the Add Existing Rules dialog box.

6. In the Add Existing Rules page, select the rules you want, and then click Move (or Move All, if you want all of them) to move them to the Selected Rules list.

   You can select multiple rules by holding down the Ctrl key as you click each rule.

7. Click OK.

8. Click Done, then click Finish.

Removing a Rule from a Rule Set

Before you remove a rule from a rule set, you can locate the various references to it by querying the rules-related Oracle Database Vault views.

See Chapter 22 for more information about Oracle Database Vault views.

To remove a rule from a rule set:

1. From Cloud Control, log into Oracle Database Vault Administrator as a user who has been granted the DV_OWNER or DV_ADMIN role.

   "Logging into Oracle Database Vault" explains how to log in.

2. In the Administration page, under Database Vault Components, click Rule Sets.

3. Select the rule set to which you want to add an existing rule, and then click Edit.

4. Click Next until you reach the Rules Associated with Rule Sets page.

5. Select the rule you want to delete and click Remove.

6. Click Done, then click Finish.

After you remove the rule from the rule set, the rule still exists. If you want, you can associate it with other rule sets. If you want to delete the rule, you can do so from the Rules page.

How Oracle Database Vault Evaluates Rules

Oracle Database Vault evaluates the rules within a rule set as a collection of expressions.

If you have set Evaluation Options to All True and if a rule evaluates to false, then the evaluation stops at that point, instead of attempting to evaluate the rest of the rules in the rule set. Similarly, if Evaluation Options is set to Any True and if a rule evaluates to true, the evaluation stops at that point. If a rule set is disabled, Oracle Database Vault evaluates it to true without evaluating its rules.

Nested Rules within a Rule Set

You can nest one or more rules within the rule set.

For example, suppose you want to create a nested rule, Is Corporate Network During Maintenance, that performs the following two tasks:

• It limits table modifications only when the database session originates within the corporate network.

• It restricts table modifications during the system maintenance window scheduled between 10:00 p.m. and 10:59 p.m.

The rule definition would be as follows:

DVF.F$NETWORK = 'Corporate' AND TO_CHAR(SYSDATE,'HH24') between '22' AND '23'

You can create it using a factor function. See "Oracle Database Vault DVF PL/SQL Factor Functions" for more information. Chapter 8 explains how to create factors.

Creating Rules to Apply to Everyone Except One User

You can also create rules to apply to everyone except one user (for example, a privileged user).

• To create a rule that excludes specific users, user the SYS_CONTEXT function.

  For example:

  SYS_CONTEXT('USERENV','SESSION_USER') = 'SUPERADMIN_USER' OR additional_rule
  

  If the current user is a privileged user, then the system evaluates the rule to true without evaluating additional_rule. If the current user is not a privileged user, then the evaluation of the rule depends on the evaluation of additional_rule.

About This Tutorial

In the following tutorial, you create an email alert that is sent when a user attempts to alter a table outside a maintenance period.

To do this, you must create a rule to set the maintenance period hours, attach this rule to a rule set, and then create a command rule to allow the user to alter the table. You then associate the rule set with this command rule, which then sends the email alert when the user attempts to use the ALTER TABLE SQL statement outside the maintenance period.

Step 1: Install and Configure the UTL_MAIL PL/SQL Package

The UTL_MAIL PL/SQL package contains a set of procedures that enable you to manage email notifications. You must manually install this package.

1. Log into the database instance as SYS using the SYSDBA administrative privilege.

   sqlplus sys as sysdba
   Enter password: password
   

2. In a multitenant environment, connect to the appropriate pluggable database (PDB).

   For example:

   CONNECT SYS@my_pdb AS SYSDBA
   Enter password: password
   

   To find the available PDBs, query the DBA_PDBS data dictionary view. To check the current PDB, run the show con_name command.

3. Install the UTL_MAIL package.

   @$ORACLE_HOME/rdbms/admin/utlmail.sql
   @$ORACLE_HOME/rdbms/admin/prvtmail.plb
   

   The UTL_MAIL package enables you to manage email. See Oracle Database PL/SQL Packages and Types Reference for more information about UTL_MAIL. However, be aware that currently, the UTL_MAIL PL/SQL package do not support SSL servers.

4. Check the current value of the SMTP_OUT_SERVER parameter, and make a note of this value so that you can restore it when you complete this tutorial.

   For example:

   SHOW PARAMETER SMTP_OUT_SERVER
   

   Output similar to the following appears:

   NAME                    TYPE              VALUE
   ----------------------- ----------------- ----------------------------------
   SMTP_OUT_SERVER         string            some_value.example.com
   

5. Issue the following ALTER SYSTEM statement:

   ALTER SYSTEM SET SMTP_OUT_SERVER="imap_mail_server.example.com";
   

   Replace imap_mail_server.example.com with the name of your SMTP server, which you can find in the account settings in your email tool. Enclose these settings in double quotation marks. For example:

   ALTER SYSTEM SET SMTP_OUT_SERVER="my_imap_mail_server.example.com"
   

6. Connect as SYS using the SYSOPER privilege and then restart the database.

   CONNECT SYS AS SYSOPER -- Or, CONNECT SYS@hrpdb AS SYSOPER
   Enter password: password
   
   SHUTDOWN IMMEDIATE
   STARTUP
   

7. Ensure that the SMTP_OUT_SERVER parameter setting is correct.

   CONNECT SYS AS SYSDBA -- Or, CONNECT SYS@hrpdb AS SYSDBA
   Enter password: password
   
   SHOW PARAMETER SMTP_OUT_SERVER
   

   Output similar to the following appears:

   NAME                    TYPE              VALUE
   ----------------------- ----------------- ----------------------------------
   SMTP_OUT_SERVER         string            my_imap_mail_server.example.com
   

Step 2: Create an Email Security Alert PL/SQL Procedure

User leo_dvowner can use the CREATE PROCEDURE statement to create the email security alert.

1. Ensure that you are connected as a user who has privileges to perform the grants described in this step, and then grant these privileges to a user who has been granted the DV_OWNER role. You should also be authorized as an owner of the Oracle System Privilege and Role Management realm.

   (Alternatively, you can select a user who has been granted the DV_ADMIN role, but for this tutorial, you will select a user who has the DV_OWNER role.)

   For example:

   CONNECT dba_psmith -- Or, CONNECT dba_psmith@hrpdb
   Enter password: password
   
   GRANT CREATE PROCEDURE, DROP ANY PROCEDURE TO leo_dvowner;
   GRANT EXECUTE ON UTL_TCP TO leo_dvowner;
   GRANT EXECUTE ON UTL_SMTP TO leo_dvowner;
   GRANT EXECUTE ON UTL_MAIL TO leo_dvowner;
   GRANT EXECUTE ON DBMS_NETWORK_ACL_ADMIN TO leo_dvowner;
   

   The UTL_TCP, UTL_SMTP, UTL_MAIL, and DBMS_NETWORK_ACL_ADMIN PL/SQL packages will be used by the email security alert that you create.

2. Connect to SQL*Plus as the DV_OWNER user.

   For example:

   CONNECT leo_dvowner -- Or, CONNECT leo_dvowner@hrpdb
   Enter password: password
   

3. Create the following procedure:

   CREATE OR REPLACE PROCEDURE email_alert AS
   msg varchar2(20000) := 'Realm violation occurred for the ALTER TABLE Command Security Policy rule set. The time is: '; 
   BEGIN
     msg := msg||to_char(SYSDATE, 'Day DD MON, YYYY HH24:MI:SS'); 
   UTL_MAIL.SEND (
       sender      => 'youremail@example.com',
       recipients  => 'recipientemail@example.com',
       subject     => 'Table modification attempted outside maintenance!',
       message     => msg); 
   END email_alert;
   /
   

   Replace youremail@example.com with your email address, and recipientemail@example.com with the email address of the person you want to receive the notification.

4. Grant the EXECUTE permission on this procedure to DVSYS.

   GRANT EXECUTE ON email_alert TO DVSYS;
   

Step 3: Configure an Access Control List File for Network Services

Before you can use PL/SQL network utility packages such as UTL_MAIL, you must configure an access control list (ACL) file that enables fine-grained access to external network services.

For detailed information about this topic, see Oracle Database Security Guide.

1. As the DV_OWNER user, in SQL*Plus, configure the following access control setting and its privilege definitions.

   BEGIN
    DBMS_NETWORK_ACL_ADMIN.APPEND_HOST_ACE(
     host       => 'SMTP_OUT_SERVER_setting',
     lower_port => 25,
     ace        =>  xs$ace_type(privilege_list => xs$name_list('smtp'),
                                principal_name => 'LEO_DVOWNER,
                                principal_type => xs_acl.ptype_db));
   END;
   /
   

   In this example:

   • lower_port: Enter the port number that your email tool specifies for its outgoing server. Typically, this setting is 25. Enter this value for both the lower_port and upper_port settings. (Currently, the UTL_MAIL package does not support SSL. If your mail server is an SSL server, then enter 25 for the port number, even if the mail server uses a different port number.)

   • principal_name: replace LEO_DVOWNER with the name of the DV_OWNER user.

   • host: For the SMTP_OUT_SERVER_setting, enter the SMTP_OUT_SERVER setting that you set for the SMTP_OUT_SERVER parameter in "Step 1: Install and Configure the UTL_MAIL PL/SQL Package". This setting should match exactly the setting that your email tool specifies for its outgoing server.

2. Commit your changes to the database.

   COMMIT;
   

3. Test the settings that you have created so far.

   EXEC EMAIL_ALERT;
   COMMIT;
   

   SQL*Plus should display a PL/SQL procedure successfully completed message, and in a moment, depending on the speed of your email server, you should receive the email alert.

   If you receive an ORA-24247: network access denied by access control list (ACL) error followed by ORA-06512: at stringline string errors, then check the settings in the access control list file.

Step 4: Create a Rule Set and a Command Rule to Use the Email Security Alert

To create the rule set and command rule, you can use DBMS_MACADM PL/SQL package.

1. As the DV_OWNER user, create the following rule set:

   BEGIN
    DBMS_MACADM.CREATE_RULE_SET(
     rule_set_name    => 'ALTER TABLE Command Security Policy', 
     description      => 'This rule set allows ALTER TABLE only during the 
                          maintenance period.', 
     enabled          => DBMS_MACUTL.G_YES,
     eval_options     => DBMS_MACUTL.G_RULESET_EVAL_ALL,
     audit_options    => DBMS_MACUTL.G_RULESET_AUDIT_FAIL,
     fail_options     => DBMS_MACUTL.G_RULESET_FAIL_SILENT,
     fail_message     => '',
     fail_code        => NULL,
     handler_options  => DBMS_MACUTL.G_RULESET_HANDLER_FAIL,
     handler          => 'leo_dvowner.email_alert');
   END;
   /
   

2. Create a rule similar to the following.

   For now, set the rule expression to be during the time you test it. For example, if you want to test it between 2 p.m. and 3 p.m., create the rule as follows:

   BEGIN
    DBMS_MACADM.CREATE_RULE(
     rule_name  => 'Restrict Access to Maintenance Period', 
     rule_expr  => 'TO_CHAR(SYSDATE,''HH24'') BETWEEN ''14'' AND ''15''');
   END;
   /
   

   Ensure that you use two single quotation marks instead of double quotation marks for HH24, 14, and 15.

   You can check the system time on your computer by issuing the following SQL statement:

   SELECT TO_CHAR(SYSDATE,'HH24') FROM DUAL;
   

   Output similar to the following appears:

   TO
   --
   14
   

   Later on, when you are satisfied that the rule works, you can update it to a time when your site typically performs maintenance work (for example, between 7 p.m. and 10 p.m), as follows:

   BEGIN
    DBMS_MACADM.UPDATE_RULE(
     rule_name  => 'Restrict Access to Maintenance Period', 
     rule_expr  => 'TO_CHAR(SYSDATE,''HH24'') BETWEEN ''16'' AND ''22''');
   END;
   /
   

3. Add the Restrict Access to Maintenance Period rule to the ALTER TABLE Command Security Policy rule set.

   BEGIN
    DBMS_MACADM.ADD_RULE_TO_RULE_SET(
     rule_set_name => 'ALTER TABLE Command Security Policy', 
     rule_name     => 'Restrict Access to Maintenance Period'); 
   END;
   /
   

4. Create the following command rule:

   BEGIN
    DBMS_MACADM.CREATE_COMMAND_RULE(
     command         => 'ALTER TABLE', 
     rule_set_name   => 'ALTER TABLE Command Security Policy', 
     object_owner    => 'SCOTT', 
     object_name     => '%', 
     enabled         => DBMS_MACUTL.G_YES);
   END; 
   /
   

5. Commit these updates to the database.

   COMMIT;
   

Step 5: Test the Email Security Alert

After the alert has been created, it is ready to be tested.

1. Connect to SQL*Plus as user SCOTT.

   For example:

   CONNECT SCOTT -- Or, CONNECT SCOTT@hrpdb
   Enter password: password
   

   If the SCOTT account is locked and expired, then a user with the DV_ACCTMGR role can unlock this account and create a new password as follows:

   ALTER USER SCOTT ACCOUNT UNLOCK IDENTIFIED BY password;
   

   Replace password with a password that is secure. See Oracle Database Security Guide for the minimum requirements for creating passwords.

2. As the user SCOTT, create a test table.

   CREATE TABLE mytest (col1 number);
   

3. Change the system time on your computer to a time when the ALTER TABLE Command Security Policy rule set takes place.

   For example, if you set the test period time to between 2 p.m. and 3 p.m., do the following:

   UNIX: Log in as root and use the date command to set the time. For example, assuming the date today is August 15, 2012, you would enter the following:

   $ su root
   Password: password
   
   $ date -s "08/15/2012 14:48:00"
   

   Windows: Double-click the clock icon, which is typically at the lower right corner of the screen. In the Date and Time Properties window, set the time to 2 p.m., and then click OK.

4. Try altering the my_test table.

   ALTER TABLE mytest ADD (col2 number);
   
   Table altered.
   

   SCOTT should be able to alter the mytest table during this time.

5. Reset the system time to a time outside the Restrict Access to Maintenance Period time.

6. Log in as SCOTT and try altering the my_test table again.

   CONNECT SCOTT -- Or, CONNECT SCOTT@hrpdb
   Enter password: password
   
   ALTER TABLE mytest ADD (col3 number);
   

   The following output should appear:

   ORA-47400: Command Rule violation for ALTER TABLE on SCOTT.MYTEST
   

   SCOTT cannot alter the mytest table. In a moment, you should receive an email with the subject header Table modification attempted outside maintenance! and with a message similar to the following:

   Realm violation occurred for the ALTER TABLE Command Security Policy rule set. The time is: Wednesday 15 AUG, 2012 14:24:25
   

7. Reset the system time to the correct time.

Step 6: Remove the Components for This Tutorial

You can remove the components that you created for this tutorial if you no longer need them.

1. Connect to SQL*Plus as the DV_OWNER user.

   CONNECT leo_dvowner -- Or, CONNECT leo_dvowner@hrpdb
   Enter password: password
   

2. In the order shown, drop the Oracle Database Vault rule components.

   EXEC DBMS_MACADM.DELETE_RULE_FROM_RULE_SET('ALTER TABLE Command Security Policy', 'Restrict Access to Maintenance Period');
   EXEC DBMS_MACADM.DELETE_RULE('Restrict Access to Maintenance Period');
   EXEC DBMS_MACADM.DELETE_COMMAND_RULE('ALTER TABLE', 'SCOTT', '%');
   EXEC DBMS_MACADM.DELETE_RULE_SET('ALTER TABLE Command Security Policy');
   

3. Drop the email_alert PL/SQL procedure.

   DROP PROCEDURE email_alert;
   

4. Connect as user SCOTT and remove the mytest table.

   CONNECT SCOTT -- Or, CONNECT SCOTT@hrpdb
   Enter password: password
   
   DROP TABLE mytest;
   

5. Connect as a user who has privileges to revoke privileges from other users.

   For example:

   CONNECT dba_psmith -- Or, CONNECT dba_psmith@hrpdb
   Enter password: password
   

6. Revoke the EXECUTE privilege on the UTL_TCP, UTL_SMTP, and UTL_MAIL PL/SQL packages from the DV_OWNER user.

   For example:

   REVOKE EXECUTE ON UTL_TCP FROM leo_dvowner;
   REVOKE EXECUTE ON UTL_SMTP FROM leo_dvowner;
   REVOKE EXECUTE ON UTL_MAIL FROM leo_dvowner;
   REVOKE EXECUTE ON DBMS_NETWORK_ACL_ADMIN FROM leo_dvowner;
   

7. Set the SMTP_OUT_SERVER parameter to its original value.

   For example:

   ALTER SYSTEM SET SMTP_OUT_SERVER="some_value.example.com";
   

8. Connect as SYS with the SYSOPER administrative privilege and then restart the database.

   CONNECT SYS AS SYSOPER -- Or, CONNECT SYS@hrpdb AS SYSOPER
   Enter password: password
   
   SHUTDOWN IMMEDIATE
   STARTUP
   

About This Tutorial

In this tutorial, you configure a rule set that defines two-person integrity (TPI), also called dual key security, dual key connection, and two-man rule security. In this type of security, two users are required to authorize an action instead of one user. The idea is that one user provides a safety check for the other user before that user can proceed with a task. Two-person integrity provides an additional layer of security for actions that potentially can be dangerous. This type of scenario is often used for tasks such as database patch updates, which is what this tutorial will demonstrate. One user, patch_user must log into perform a database patch upgrade, but the only way that he can do this is if his manager, patch_boss is already logged in. You will create a function, rules, a rule set, and a command rule to control patch_user's ability to log in.

Step 1: Create Users for This Tutorial

You must create two users for this tutorial, patch_boss and patch_user.

• patch_boss acts in a supervisory role: If patch_boss is not logged in, then the patch_user user cannot log in.

• patch_user is the user who is assigned to perform the patch upgrade. However, for this tutorial, user patch_user does not actually perform a patch upgrade. He only attempts to log in.

To create the users:

1. Log into the database instance as a user who has been granted the DV_ACCTMGR role.

   For example:

   sqlplus bea_dvacctmgr
   Enter password: password
   

2. In a multitenant environment, connect to the appropriate PDB.

   For example:

   CONNECT bea_dvacctmgr@hrpdb
   Enter password: password
   

   To find the available PDBs, query the DBA_PDBS data dictionary view. To check the current PDB, run the show con_name command.

3. Create the following users and grant them the CREATE SESSION privilege.

   GRANT CREATE SESSION TO patch_boss IDENTIFIED BY password;
   GRANT CREATE SESSION TO patch_user IDENTIFIED BY password;
   

   Replace password with a password that is secure. See Oracle Database Security Guide for the minimum requirements for creating passwords.

4. Connect as user SYS with the SYSDBA administrative privilege.

   CONNECT SYS AS SYSDBA -- Or, CONNECT SYS@hrpdb AS SYSDBA
   Enter password: password
   

5. Grant the following privileges to the DV_OWNER or DV_ADMIN user.

   For example:

   GRANT CREATE PROCEDURE TO leo_dvowner;
   GRANT SELECT ON V_$SESSION TO leo_dvowner;
   

   The V_$SESSION table is the underlying table for the V$SESSION dynamic view.

In a real-world scenario, you also would log in as the DV_OWNER user and grant the DV_PATCH_ADMIN role to user patch_user (but not to patch_boss). But because you are not really going to perform a database patch upgrade in this tutorial, you do not need to grant this role to user patch_user.

Step 2: Create a Function to Check if User patch_boss Is Logged In

The function that you must create, check_boss_logged_in, does just that: When user patch_user tries to log into the database instance, it checks if user patch_boss is already logged in by querying the V$SESSION data dictionary view.

1. Connect as a user who has been granted the DV_OWNER or DV_ADMIN role.

   For example:

   CONNECT leo_dvowner -- Or, CONNECT leo_dvowner@hrpdb
   Enter password: password
   

2. Create the check_boss_logged_in function as follows:

   CREATE OR REPLACE FUNCTION check_boss_logged_in
   return varchar2
   authid definer as 
    
   v_session_number number := 0;
   v_allow varchar2(10)    := 'TRUE';
   v_deny varchar2(10)     := 'FALSE';
    
   BEGIN
     SELECT COUNT(*) INTO v_session_number
     FROM SYS.V_$SESSION
     WHERE USERNAME = 'PATCH_BOSS'; -- Enter the user name in capital letters.
    
    IF v_session_number > 0
     THEN RETURN v_allow;
    ELSE
     RETURN v_deny;
    END IF;
   END check_boss_logged_in;
   /
   

3. Grant the EXECUTE privilege on the check_boss_logged_in function to the DVSYS schema.

   GRANT EXECUTE ON check_boss_logged_in to DVSYS;
   

Step 3: Create Rules, a Rule Set, and a Command Rule to Control the Users' Access

Next, you must create two rules, a rule set to which you will add them, and a command rule. The rule set triggers the check_boss_logged_in function when user patch_user tries to logs in to the database.

1. Connect as a user who has been granted the DV_OWNER or DV_ADMIN role.

   For example:

   CONNECT leo_dvowner -- Or, CONNECT leo_dvowner@hrpdb
   Enter password: password
   

2. Create the Check if Boss Is Logged In rule, which checks that the patch_user user is logged in to the database. In the definition, replace leo_dvowner with the name of the DVOWNER or DV_ADMIN user who created the check_boss_logged_in function.

   If the check_boss_logged_in function returns TRUE (that is, patch_boss is logged in to another session), then patch_user can log in.

   BEGIN
     DBMS_MACADM.CREATE_RULE(
      rule_name => 'Check if Boss Is Logged In',
      rule_expr => 'SYS_CONTEXT(''USERENV'',''SESSION_USER'') = ''PATCH_USER'' and leo_dvowner.check_boss_logged_in =  ''TRUE'' ');
   END;
   /
   

   Enter the user name, PATCH_USER, in upper-case letters, which is how the SESSION_USER parameter stores it.

3. Create the Allow Connect for Other Database Users rule, which ensures that the user logged in (patch_user) is not user patch_boss. It also enables all other valid users to log in.

   BEGIN
    DBMS_MACADM.CREATE_RULE(
     rule_name => 'Allow Connect for Other Database Users',
     rule_expr => 'SYS_CONTEXT(''USERENV'',''SESSION_USER'') != ''PATCH_USER''');
   END;
   /
   COMMIT;
   

4. Create the Dual Connect for Boss and Patch rule set, and then add the two rules to it.

   BEGIN
       DBMS_MACADM.CREATE_RULE_SET(
        rule_set_name => 'Dual Connect for Boss and Patch',
        description => 'Checks if both boss and patch users are logged in.',
        enabled           => DBMS_MACUTL.G_YES,
        eval_options      => 2,
        audit_options     => DBMS_MACUTL.G_RULESET_AUDIT_FAIL,
        fail_options      => DBMS_MACUTL.G_RULESET_FAIL_SILENT,
        fail_message      =>'',
        fail_code         => NULL,
        handler_options   => DBMS_MACUTL.G_RULESET_HANDLER_OFF,
        handler           => ''
        );
   END;
   /
   
   BEGIN
       DBMS_MACADM.ADD_RULE_TO_RULE_SET(
        rule_set_name     => 'Dual Connect for Boss and Patch',
        rule_name         => 'Check if Boss Is Logged In'
      );
   END;
   /
   
   BEGIN
       DBMS_MACADM.ADD_RULE_TO_RULE_SET(
        rule_set_name     => 'Dual Connect for Boss and Patch',
        rule_name         => 'Allow Connect for Other Database Users'
      );
   END;
   /
   

5. Create the following CONNECT command rule, which permits user patch_user to connect to the database only if patch_boss is already logged in.

   BEGIN
      DBMS_MACADM.CREATE_COMMAND_RULE(
       command             => 'CONNECT',
       rule_set_name      => 'Dual Connect for Boss and Patch',
       object_owner       => '%',
       object_name        => '%',
       enabled            => DBMS_MACUTL.G_YES);
   END;
   /
   COMMIT;
   

Step 4: Test the Users' Access

After the rules have been created, they are ready to be tested.

1. Exit SQL*Plus.

   EXIT
   

2. Create a second shell, for example:

   xterm &
   

3. In the first shell, try to log in as user patch_user.

   sqlplus patch_user -- Or, sqlplus patch_user@hrpdb
   Enter password: password
   
   ERROR:
   ORA-47400: Command Rule violation for CONNECT on LOGON
   
   Enter user-name:
   

   User patch_user cannot log in until user patch_boss is already logged in. (Do not try the Enter user-name prompt yet.)

4. In the second shell and then log in as user patch_boss.

   sqlplus patch_boss -- Or, sqlplus patch_boss@hrpdb
   Enter password: password
   Connected. 
   

   User patch_boss can log in.

5. Go back to the first shell, and then try logging in as user patch_user again.

   Enter user_name: patch_user
   Enter password: password
   

   This time, user patch_user is deemed a valid user, so now he can log in.

Step 5: Remove the Components for This Tutorial

You can remove the components that you created for this tutorial if you no longer need them.

1. In the session for the user patch_boss, exit SQL*Plus and then close the shell.

   EXIT
   

2. In the first shell, connect the DV_ACCTMGR user and remove the users you created.

   CONNECT bea_dvacctmgr -- Or, CONNECT bea_dvacctmgr@hrpdb
   Enter password: password
   
   DROP USER patch_boss;
   DROP USER patch_user;
   

3. Connect as a user SYS with the SYSDBA administrative privilege and revoke the privileges that you had granted to the DV_OWNER or DV_ADMIN user.

   CONNECT SYS AS SYSDBA -- Or, CONNECT SYS@hrpdb AS SYSDBA
   Enter password: password
   
   REVOKE CREATE PROCEDURE FROM leo_dvowner;
   REVOKE SELECT ON V_$SESSION FROM leo_dvowner;
   

4. Connect as the DV_OWNER or DV_ADMIN user and drop the rules, rule set, and command rule, in the order shown.

   CONNECT leo_dvowner -- Or, CONNECT leo_dvowner@hrpdb
   Enter password: password
   
   DROP FUNCTION check_boss_logged_in;
   EXEC DBMS_MACADM.DELETE_COMMAND_RULE('CONNECT', '%', '%');
   EXEC DBMS_MACADM.DELETE_RULE_FROM_RULE_SET('Dual Connect for Boss and Patch', 'Check if Boss Is Logged In');
   EXEC DBMS_MACADM.DELETE_RULE_FROM_RULE_SET('Dual Connect for Boss and Patch', 'Allow Connect for Other Database Users');
   EXEC DBMS_MACADM.DELETE_RULE('Check if Boss Is Logged In');
   EXEC DBMS_MACADM.DELETE_RULE('Allow Connect for Other Database Users');
   EXEC DBMS_MACADM.DELETE_RULE_SET('Dual Connect for Boss and Patch');
   COMMIT;