Archives of the TeradataForum
Message Posted: Mon, 03 Jun 2002 @ 15:03:56 GMT
| Subj: || || Re: Teradata Security Question |
| From: || || Cornelius Meade |
In short I do not think there is a Teradata centric way limit access as you describe as all the system requires is a valid user id and
password. It does not matter what interface this information is presented through....
Here us one thing you could possibly consider however....You can use a hidden password that only your application or access tool knows
about. For example your users would log on through BusinessObjects security with a userid and password that to their knowledge is the
database user and password. At the database level the user account could be the same but you would create the account using a different
password that is only known in the BO layer. When BO validates the initial user/password it then submits any transactions on the users
behalf to the database using the user/bo_internal_pwd. This way the user accounts are still unique to each individual user however the user
does not know the password for the actual database account. This would help preclude them from using some other path to connect to the
database other than the provided BO interface.