This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
integration:rdbms:oracle:databases [2011/04/05 20:24] doc |
integration:rdbms:oracle:databases [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 52: | Line 52: | ||
| === Oracle Security === | === Oracle Security === | ||
| - | Omnidex provides two methods of supporting Oracle security. The first option is for administrators to register a single user and password in the Omnidex Environment File to access an Oracle database. The second option is to pass a user and password in the [[dev:connections:home|Omnidex Connection String]]. This use user and password will be passed directly to Oracle to access the database. Administrators should insure that the user and password provides access to all of the database objects referenced in the Omnidex Environment Files. | + | Omnidex provides two methods of supporting Oracle security. |
| + | |||
| + | * Administrators can register a user and password in the Omnidex Environment File. This user and password will always be used to access the Oracle database, and no users and passwords will be needed from the application. | ||
| + | * The application can pass a user and password in the [[dev:connections:home|Omnidex Connection String]]. This user and password is then passed directly to Oracle to access the database. | ||
| + | |||
| + | One of these approaches must be used to allow connections to the Oracle database. Administrators should insure that the user and password provides access to all of the database objects referenced in the Omnidex Environment Files. | ||
| ===== ===== | ===== ===== | ||