Skip to content

Commit 06ab8f3

Browse files
committed
OAG DBAT integration asset
1 parent de953db commit 06ab8f3

File tree

1 file changed

+18
-13
lines changed
  • security/identity-and-access-management/oracle-access-governance/dbat-os-accounts-sample

1 file changed

+18
-13
lines changed

security/identity-and-access-management/oracle-access-governance/dbat-os-accounts-sample/README.md

Lines changed: 18 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ The following components are required and assumed to already be available in thi
2525

2626
Please ensure the requirements listed above have been satisfied.
2727

28-
Once a database installation/instance is available follow the below steps to deploy the provided sample SQL schema:
28+
**Once a database installation/instance is available** follow the below steps to deploy the provided sample SQL schema:
2929

3030
1. Connect to the database as dba (with sysdba role) and create a schema user for the purposes of the integration, by running:
3131

@@ -55,17 +55,24 @@ GRANT DROP ANY PROCEDURE TO OAG;
5555

5656
2. Connect to the database as the newly create OAG user (using the password you've set with the above command), and execute the `OS_Account.sql` file. This will create all the quired table schema and populate it with sample data.
5757

58-
In order to achieve the integration in Oracle Access Governance, follow the below steps to create a new orchestrated system:
58+
**In order to achieve the DBAT integration in Oracle Access Governance**, follow the below steps to create a new orchestrated system:
59+
60+
**Note:** The Connect URL format provided below is meant for pluggable databases using DB service names. Please adjust it as needed. All types of jdbc URL formats are supported, including basic SID-based URLs such as: `jdbc:oracle:thin:@hostname:port:SID`.
61+
62+
1. Go to **Service Administration -> Manage orchestrated systems**.
63+
2. Click on **+ Add an Orchestrated system**.
64+
3. In the **Select System** step, pick `Database Application Table (Oracle DB)`, and click on Next.
65+
4. In the **Enter Details** step, enter the details provided below. Optionally untick `This is the authoritative source for my identities.` should you want to create the identities through other means, otherwise, for the purposes of this example, the identities will be imported using data from the **OS_ACCOUNT** table. Click on Next.
66+
67+
```
68+
What do you want to call this system?: OS Account
69+
How do you want to describe this system: OS level user account
70+
```
5971

60-
1. Go to Service Administration -> Manage orchestrated systems.
61-
2. Click on + Add an Orchestrated system.
62-
3. In the "Select System" step, pick `Database Application Table (Oracle DB)`, and click on Next.
63-
4. In the "Enter Details" step, enter the following details: ```What do you want to call this system?: OS Account
64-
How do you want to describe this system: OS level user account``` Optionally untick `This is the authoritative source for my identities.` should you want to create the identities through other means, otherwise for the purposes of this example, the identities will be imported using data from the OS_ACCOUNT table. Click on Next.
6572
5. Click on Confirm if you are using both authoritative and manager permission integration modes.
66-
6. In the "Add Owners" step, use the default values and click on Next.
67-
7. In the "Account Settings" step, use the default values and click on Next.
68-
8. In the "Integration" step, enter the following details, adjusted to your particular deployment settings. Leave the rest of the fields on their default values, and click on Add.
73+
6. In the **Add Owners** step, use the default values and click on Next.
74+
7. In the **Account Settings** step, use the default values and click on Next.
75+
8. In the **Integration** step, enter the following details, adjusted to your particular deployment settings. Leave the rest of the fields on their default values, and click on Add.
6976

7077
```
7178
Easy Connect URL for Oracle Database: jdbc:oracle:thin:@//hostname:port/dbservicename
@@ -82,11 +89,9 @@ User account table password column mapping: OS_ACCOUNT:PASSWORD
8289
User account table status column mapping: OS_ACCOUNT:STATUS
8390
```
8491

85-
9. On the "Finish up" step, first click on the `Download` link and save the agent package, then select `Activate and prepare the data load with the provided defaults` and click on I'm done.
92+
9. On the **Finish up** step, first click on the `Download` link and save the agent package, then select `Activate and prepare the data load with the provided defaults` and click on I'm done.
8693
10. Use the downloaded `OS_Account.zip` archive to deploy the OAG agent as per the steps covered in [this guide](https://docs.oracle.com/en/cloud/paas/access-governance/lllho/index.html#GUID-67A8B48F-9358-4B95-A36C-5871E3726FAB). Once the agent is deployed and started, it will automatically validate the configurations and import the data into OAG, and you can start using the integration.
8794

88-
**Note:** The above URL format is meant for pluggable databases using DB service names. Please adjust it as needed. All types of jdbc URL formats are supported, including basic SID-based URLs such as: `jdbc:oracle:thin:@hostname:port:SID`.
89-
9095
Please also see the useful link below for more detailed deployment steps.
9196

9297
# Useful Links

0 commit comments

Comments
 (0)