...
Anchor |
---|
| isolateconnector |
---|
| isolateconnector |
---|
|
...
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.
It is accomplished with the following tasks:
...
.
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 , in the TFO_CONNECTOR schema/user.
- Create a new uAchieve daemon.
- Grant select, insert, update, and delete privileges on the newly created JOB_QUEUE_xxx tables to the TFO_CONNECTOR schema/user.
- Grant select, insert, update, and delete privileges on the newly created JOB_QUEUE_xxx tables
- Make sure the database user for the uAchieve daemon has
- as well as select 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.
- By using an empty Create JOB_QUEUE_xxx, CURRENT_JOBS and STU_ACADREC table tables, in the user/schema for the isolationTFO_CONNECTOR schema/user.
- Install the uAchieve server into a different directory, edit create daemon.