 |
 |
Archives of the TeradataForum
Message Posted: Fri, 16 Feb 2001 @ 20:45:50 GMT
Subj: | | Re: Qualifying on encrypted passwordstring |
|
From: | | John Hall |
The blunt answer is 'No'.
Why not simply go ahead and log-on the user without taking the additional step of first checking to see if it's valid user? That way,
Teradata handles all the security/user issues (ie- user/password validation, password aging, priority, etc). From your description, it
sounds like your application does one log-on to see if the user can log-on and then there is a second log-on for the user before any actual
work will be done. That sounds complicated and it doesn't do anything to improve the security of the Teradata.
| |