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.
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:
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
Grant the user permission to connect to the Oracle Database.
Grant user management permissions.
Grant role management permissions.
Grant table management permissions.
Grant the user permissions to grant permissions to Oracle users.
Using the credentials from step 1, for the database instance.
You can also input the user credentials directly into the Apono UI during the .
You can now .
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:
On the tab, click Oracle Database. The Connect Integration page appears.
Under Discovery, click one or more resource types to sync with Apono.
Click Next. The Apono connector section expands.
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 (, , , ).
Click Next. The Integration Config section expands.
Define the Integration Config settings.
Now that you have completed this integration, you can that grant permission to your Oracle Database resources.
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
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.
Click Next. The Secret Store section expands.
Click Next. The Get more with Apono section expands.
Define the Get more with Apono settings.
Credential Rotation
(Optional) Number of days after which the database credentials must be rotated Learn more about the .
User cleanup after access is revoked (in days)
(Optional) Defines the number of days after access has been revoked that the user should be deleted
Learn more about .
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 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.
Click Confirm.
Make any additional edits.
Deploy the code in your Terraform.
Refer to Integration Config Metadata for more details about the schema definition.
Apono Connector
On-prem connection serving as a bridge between an Oracle Database instance and Apono:
Oracle Database Information
Information for the database instance to be integrated:
Hostname
Port number
Admin access to Oracle
The Admin must be able to create users and manage roles in Oracle
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
CREATE USER apono_connector IDENTIFIED BY password;
ALTER USER apono_connector DEFAULT TABLESPACE users;
ALTER USER apono_connector TEMPORARY TABLESPACE temp;
ALTER USER apono_connector QUOTA UNLIMITED ON users;GRANT CREATE SESSION TO apono_connector;
GRANT CONNECT, RESOURCE TO apono_connector;GRANT CREATE USER TO apono_connector;
GRANT ALTER USER TO apono_connector;
GRANT DROP USER TO apono_connector;
GRANT ALTER SYSTEM TO apono_connector;
GRANT SELECT_CATALOG_ROLE TO apono_connector;GRANT GRANT ANY ROLE TO apono_connector;
GRANT CREATE ROLE TO apono_connector;
GRANT DROP ANY ROLE TO apono_connector;GRANT GRANT ANY OBJECT PRIVILEGE TO apono_connector;GRANT GRANT ANY PRIVILEGE TO apono_connector; 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.