Connector and uAchieve Audits

uAchieve Server Minimum Database Access

This section is important when the database user used by the uAchieve server is different than the schema owner of the uachieve tables. If the database user used by the uAchieve server is the same as the database owner of the uAchieve tables, the points in this section aren't necessary.

When the database user used by the uAchieve server is different than the schema owner of the uachieve tables, the database user for the uAchieve server must have the following minimum access (synonyms and privileges):

• Private synonyms are required for all tables identified in this section.
• Select, insert, update, and delete privileges on the CURRENT_JOBS and JOB_QUEUE_xxx tables.

• Select privilege on the following uAchieve tables:

  Select Privileges

  CHART_CATEGORIES
  COM
  CRS_CONVERT
  DPROG
  DPROG_REQ
  GMASTER
  MASTREF
  MASTREF_ADDRESS
  MASTREF_SEG
  REPEAT
  REQ_MAIN
  REQ_TEXT
  REQ_XY
  STRING
  STRING_CRSE
  SUB_REQ
  SUB_REQ_AR
  SUB_REQ_TEXT
  STU_ACADREC
  TCA_MASTER
  TCA_RULE
  TCA_SOURCE
  TCA_TARGET

Isolating the Connector From Your School's Existing uAchieve Audit Data

Some schools want to prevent the Connector from accessing the audit data contained in the JOB_QUEUE_xxx tables used by their existing uAchieve Server. 

The alternatives below assume this initial setup, prior to performing the isolation steps:

1. Db user/schema UACHIEVE owns all UACHIEVE tables.
2. The uAchieve server connects to the database as the UACHIEVE user.
3. Db user/schema TFO_CONNECTOR has access (privileges and synonyms) to the UACHIEVE schema tables as indicated above.
4. The Transferology Connector connects to the database as the TFO_CONNECTOR user.

The following sections show the two alternatives.

Isolation via 3 Database Users

This isolation requires three database users and is the most secure. 

Coming soon!

• Grant select, insert, update, and delete privileges on the newly created JOB_QUEUE_xxx tables to the TFO_CONNECTOR schema/user.
• Make sure the database user for the uAchieve daemon has 
• as well as select privilege on the tables listed above but not STU_ACADREC.

Isolation via 2 Database Users

This isolation only requires two database users. It is slightly less secure than the above 3 Database User alternative.

Database user specifics:

• Db user/schema UACHIEVE owns all UACHIEVE tables.
• Db user/schema TFO_CONNECTOR has access (privileges and synonyms) to the UACHIEVE schema tables as indicated above, with exception to the JOB_QUEUE_xxx, CURRENT_JOBS and STU_ACADREC tables which will also exist in the TFO_CONNECTOR schema.

It is accomplished with the following tasks:

• Grant select privilege on the tables listed above but not STU_ACADREC.
• Create JOB_QUEUE_xxx, CURRENT_JOBS and STU_ACADREC tables, in the TFO_CONNECTOR schema/user.
• Install the uAchieve server into a different directory, edit create  daemon.