Subject | IB Logon |
---|---|
Author | Dion |
Post date | 2001-11-30T04:40:48Z |
Hi All,
Has anybody been able to securely allow a DBA to administer user rights seperately from IB(or any other DB for that matter). What I mean is storing user rights in a seperate table. This means that the logon names are not save to IB system tables. The problem I found is hiding the initial app logon user name and password. Where do you hide the user name and password the app needs to initially logon in order to get access to the other user table in order to authenticate user access, in a secure fashion?
Will burying it in the app have to do?
Regards,
Dion.
[Non-text portions of this message have been removed]
Has anybody been able to securely allow a DBA to administer user rights seperately from IB(or any other DB for that matter). What I mean is storing user rights in a seperate table. This means that the logon names are not save to IB system tables. The problem I found is hiding the initial app logon user name and password. Where do you hide the user name and password the app needs to initially logon in order to get access to the other user table in order to authenticate user access, in a secure fashion?
Will burying it in the app have to do?
Regards,
Dion.
[Non-text portions of this message have been removed]