Oracle Database

Create an integration to manage access to Oracle Database tables and custom roles

Oracle Database is a relational database management system (RDBMS) developed by Oracle Corporation. It enables organizations to store, manage, and retrieve data using Structured Query Language (SQL). The database includes features for ensuring data integrity, performing backup and recovery, controlling access, and tuning performance.

Oracle Database supports both on-premises and cloud-based deployments through Oracle Cloud Infrastructure.

Through this integration, Apono helps you securely manage just-in-time, just-enough access to your Oracle Database, tables and custom roles.

---

Prerequisites

Apono Connector	On-prem connection serving as a bridge between an Oracle Database instance and Apono: AWS Azure GCP Kubernetes
Oracle Database Information	Information for the database instance to be integrated: Hostname Port number

---

Create an Oracle Database user

You must create a user in your Oracle Database instance for the Apono connector.

Use the following steps to create a user and grant it permissions to your databases:

1. In your preferred client tool, create a new user. Be sure to set a strong password for the user.

The password must be a minimum of 9 characters and satisfy the following minimum requirements:

• 2 lowercase letters

• 2 uppercase letter

• 2 numbers (0-9)

• 2 special characters

• Cannot have 3 consecutive identical characters

• Have 4 different characters than the previous password

• Cannot contain, repeat, or reverse the user name

CREATE USER apono_connector IDENTIFIED BY password;

1. Grant the user permission to connect to the Oracle Database.

GRANT CREATE SESSION TO apono_connector;

1. Expose databases to the user. This allows Apono to view database names without accessing the contents of each database.

GRANT SELECT ANY TABLE TO apono_connector;

1. Grant the user permissions to query data from any object, create new user accounts, modify existing user accounts, and remove user accounts from the database.

GRANT SELECT, CREATE, ALTER, DELETE FROM DBA_USERS TO apono_connector;

1. Using the credentials from step 1, create a secret for the database instance.

You can also input the user credentials directly into the Apono UI during the integration process.

You can now integrate Oracle Database.

---

Integrate Oracle Database

Oracle Database tile

You can also use the steps below to integrate with Apono using Terraform.

In step 11, instead of clicking Confirm, follow the Are you integrating with Apono using Terraform? guidance.

Follow these steps to complete the integration:

1. On the Catalog tab, click Oracle Database. The Connect Integration page appears.

2. Under Discovery, click one or more resource types to sync with Apono.

Apono automatically discovers and syncs all the instances in the environment. After syncing, you can manage access flows to these resources.

1. Click Next. The Apono connector section expands.

2. From the dropdown menu, select a connector. Choosing a connector links Apono to all the services available on the account where the connector is located.

If the desired connector is not listed, click + Add new connector and follow the instructions for creating a connector (AWS, Azure, GCP, Kubernetes).

1. Click Next. The Integration Config section expands.

2. Define the Integration Config settings.

   Setting	Description
   Integration Name	Unique, alphanumeric, user-friendly name used to identify this integration when constructing an access flow
   Hostname	Hostname of the Oracle Database instance to connect
   Port	Port value for the instance By default, Apono sets this value to 1521.
   Service Name	Name of the service By default, Apono sets this value to ORCL.

3. Click Next. The Secret Store section expands.

4. Associate the secret or credentials.

5. Click Next. The Get more with Apono section expands.

6. Define the Get more with Apono settings.

   Setting	Description
   Credential Rotation	(Optional) Number of days after which the database credentials must be rotated
   Custom Access Details	(Optional) Instructions explaining how to access this integration's resources Upon accessing an integration, a message with these instructions will be displayed to end users in the User Portal. The message may include up to 400 characters. To view the message as it appears to end users, click Preview.
   Integration Owner	(Optional) Fallback approver if no resource owner is found Follow these steps to define one or several integration owners: From the Attribute dropdown menu, select User or Group under the relevant identity provider (IdP) platform. From the Value dropdown menu, select one or multiple users or groups. NOTE: When Resource Owner is defined, an Integration Owner must be defined.
   Resource Owner	(Optional) Group or role responsible for managing access approvals or rejections for the resource Follow these steps to define one or several resource owners: Enter a Key name. This value is the name of the tag created in your cloud environment. From the Attribute dropdown menu, select an attribute under the IdP platform to which the key name is associated. Apono will use the value associated with the key (tag) to identify the resource owner. When you update the membership of the group or role in your IdP platform, this change is also reflected in Apono. NOTE: When this setting is defined, an Integration Owner must also be defined.

7. Click Confirm.

💡Are you integrating with Apono using Terraform?

If you want to integrate with Apono using Terraform, follow these steps instead of clicking Confirm:

1. At the top of the screen, click View as Code. A modal appears with the completed Terraform configuration code.

2. Click to copy the code.

3. Make any additional edits.

4. Deploy the code in your Terraform.

Refer to Integration Config Metadata for more details about the schema definition.

Now that you have completed this integration, you can create access flows that grant permission to your Oracle Database resources.