Oracle
Automate the fulfillment of data subject access, deletion, opt-out, and identifier retrieval requests in Oracle.
Configuration
Create a Connection object with an Oracle ConnectorType to instantiate a connection. Once the object has been created and the credentials have been stored, place the object in the RMAgentConfig connections
array.
Example Configuration
{
"name": "Accounts DB",
"uuid": "e887952b-4bde-4344-bd1d-c9a46805ebed",
"capabilities": ["privacy/access","privacy/delete", "privacy/optout", "privacy/identifiers"],
"mode": "live",
"connector_type": "OracleDB",
"queries": {
"identifiers": {
"phone_number": [
"CALL get_phone_number_proc(:email)"
]
},
"access": ["CALL access_sproc(:email)"],
"delete": ["CALL delete_sproc(:email)"],
"optout": ["CALL optout_sproc(:email)"]
},
"credentials_location": "arn:aws:secretsmanager:Region:AccountId:secret:datagrail.postgres"
}
Credential Creation
The Oracle connection authenticates with your server using username and password. Create a new secret in you credentials manager with the following key/value pairs:
{
"user": "<DB username>",
"password": "<DB password>",
"server": "<server domain name or IP address>",
"port": "<port, e.g. 1521>",
"database": "<DB, e.g. BikeStores>"
}
Labels, replication, and other settings, please set as necessary.
Copy the name of the secret and insert it in as the value of the credentials_location
parameter of the connection.
Query Syntax and Parameter Binding
The Queries object allows query strings to be dynamically formatted with identifiers. Identifiers are passed individually to queries and are bound to the variables in the operation. Variables are specified using the named parameter style, e.g. ...WHERE email=:email
.
Disclaimer: The information contained in this message does not constitute as legal advice. We would advise seeking professional counsel before acting on or interpreting any material.