This post was originally published on this site

Since I’m always short of time for a longer blog post, I’ll just try a short one. Intended as a mini-series, I will show different configuration examples for Oracle Enterprise User Security. Today I’ll start with the configuration of EUS based proxy privileges. The environment I use is DOE, my Docker based Oracle Engineering environment. In particular the EUS configuration. For more information, see the corresponding GitHub repository oehrlis/doe respectively in the folder eus for the EUS specific environment.

Background

Database proxy privileges are used relatively often to give certain users rights to access a different schema. The user authenticates himself with his credentials and becomes a proxy user in the database. Below an example where the user RMAN, gets access to a different schema, specifically an other RMAN catalog schema (see also blog post about SEPS and RMAN).


CREATE USER rman IDENTIFIED BY welcome1;
CREATE USER rman19000 NO AUTHENTICATION QUOTA UNLIMITED ON rman_data;
GRANT RECOVERY_CATALOG_OWNER TO rman19000;
ALTER USER rman19000 GRANT CONNECT THROUGH rman;
ALTER USER rman19000 DEFAULT TABLESPACE rman_data;

The following users were created

  • RMAN1900 is the schema owner for an Oracle 19c RMAN catalog stored in the tablespace RMAN_DATA. The user is created without any authentication but with a proxy privilege for the user RMAN.
  • RMAN is the user which will be used to connect to the catalog. There are other catalogs as well but not shown in this example

SQL> CONNECT rman[RMAN19000]/welcome1@CATALOG
Connected.
SQL> SHOW USER
USER IS "RMAN19000"
SQL> SELECT sys_context('userenv','PROXY_USER') PROXY_USER, sys_context('userenv','SESSION_USER') SESSION_USER FROM dual;

PROXY_USER SESSION_USER
---------- ---------------
RMAN       RMAN19000D

With pure database authentication or authorisation, the configuration of proxy users is easy. With Enterprise User Security, proxy privileges are no longer managed in the database but in the directory. Let’s take a look at that.

Database Configuration

For Enterprise User Security based proxy privileges, only ENTERPRISE USERS is specified in the database. The rest is done in the OracleContext of the directory. See also ALTER USER in Oracle® Database SQL Language Reference 19c.


ALTER USER scott GRANT CONNECT THROUGH ENTERPRISE USERS;

Enterprise User Security Configuration

The configuration can be either done via Oracle Enterprise Manager Cloud Control as documented in Oracle® Database Enterprise User Security Administrator’s Guide 19c or with the command line utility eusm. I prefer the command line utility as I often do not have an OEM by hand.

  • Create the proxy permission in the directory.

eusm createProxyPerm proxy_permission="Scott Proxy"
domain_name="OracleDefaultDomain"
realm_dn="dc=trivadislabs,dc=com" ldap_host=eusoud.trivadislabs.com ldap_port=1389
ldap_user_dn=cn=eusadmin,cn=oraclecontext ldap_user_password=$(cat /u01/common/etc/eusadmin_pwd.txt)
  • Define a target user for this proxy permission.

eusm addTargetUser proxy_permission="Scott Proxy"
database_name="TEUS01"
target_user="SCOTT" dbuser="system" dbuser_password=$(cat /u00/app/oracle/admin/TEUS01/etc/TEUS01_password.txt)
dbconnect_string="eusdb.trivadislabs.com:1521/TEUS01.trivadislabs.com"
domain_name="OracleDefaultDomain"
realm_dn="dc=trivadislabs,dc=com" ldap_host=eusoud.trivadislabs.com ldap_port=1389
ldap_user_dn=cn=eusadmin,cn=oraclecontext ldap_user_password=$(cat /u01/common/etc/eusadmin_pwd.txt)
  • Explicit granting of proxy permission to the user KING. Can also be assigned to a group.

eusm grantProxyPerm proxy_permission="Scott Proxy"
user_dn="cn=Ben King,ou=Senior Management,ou=People,dc=trivadislabs,dc=com"
domain_name="OracleDefaultDomain"
realm_dn="dc=trivadislabs,dc=com" ldap_host=eusoud.trivadislabs.com ldap_port=1389
ldap_user_dn=cn=eusadmin,cn=oraclecontext ldap_user_password=$(cat /u01/common/etc/eusadmin_pwd.txt)
  • Display the proxy permissions defined for the EUS default domain.

eusm listProxyPermissions domain_name="OracleDefaultDomain"
realm_dn="dc=trivadislabs,dc=com" ldap_host=eusoud.trivadislabs.com ldap_port=1389
ldap_user_dn=cn=eusadmin,cn=oraclecontext ldap_user_password=$(cat /u01/common/etc/eusadmin_pwd.txt)
  • Display information for the proxy permission Scott Proxy

eusm listProxyPermissionInfo proxy_permission="Scott Proxy"
domain_name="OracleDefaultDomain"
realm_dn="dc=trivadislabs,dc=com" ldap_host=eusoud.trivadislabs.com ldap_port=1389
ldap_user_dn=cn=eusadmin,cn=oraclecontext ldap_user_password=$(cat /u01/common/etc/eusadmin_pwd.txt)
  • Display proxy permissions for the user KING.

eusm listProxyPermissionsOfUser
user_dn="cn=Ben King,ou=Senior Management,ou=People,dc=trivadislabs,dc=com"
realm_dn="dc=trivadislabs,dc=com" ldap_host=eusoud.trivadislabs.com ldap_port=1389
ldap_user_dn=cn=eusadmin,cn=oraclecontext ldap_user_password=$(cat /u01/common/etc/eusadmin_pwd.txt)

Using the Proxy Permissions

Let’s test the permissions and connect as user KING.

  • Regular connection to the database

SQL> CONNECT king/welcome1@TEUS01
Connected.
SQL> SHOW USER
USER IS "KING"
SQL> SELECT sys_context('userenv','PROXY_USER') PROXY_USER , sys_context('userenv','SESSION_USER') SESSION_USER FROM dual;

PROXY_USER  SESSION_USER
--------------- ---------------
                KING
  • Proxy connection to the database

SQL> CONNECT king[SCOTT]/welcome1@TEUS01
Connected.
SQL> SHOW USER
USER IS "SCOTT"
SQL> SELECT sys_context('userenv','PROXY_USER') PROXY_USER , sys_context('userenv','SESSION_USER') SESSION_USER FROM dual;

PROXY_USER  SESSION_USER
--------------- ---------------
KING            SCOTT

Conclusion

Configuration of proxy permissions in connection with Oracle Enterprise User Security is not as complicated as you might think. It is also useful if shared global users need access to certain schemas. For example, a power user is allowed to access the application schema.