|
Archives of the TeradataForumMessage Posted: Tue, 20 Feb 2001 @ 18:01:09 GMT
Hi, We are looking for a satisfactory method of logon security from the mainframe to Teradata for batch jobs. At present we store the batch user ID and password in a PDS member which is secured by ACF2 on the mainframe. Teradata utilities, Fastload, Multiload etc read this PDS member and use it to log on. The problem is that the password expires and requires manual update. We need to expire user passwords regularly. We understand that the password expiry feature is at system level, and that individual User IDs can't be set to have non-expiring passwords if the system parameter is set for password expiry. We would have liked to use SECLOGON but have never got this to work with ACF2. We are also investigating some automated method of updating the password on Teradata and simultaneously updating the PDS member on the mainframe which stores the password. We would like to find a solution which would not require manual intervention and would give us sufficient security that the batch user ID and password would be adequately secured. Does anyone have experience of using ACF2 with SECLOGON? What other techniques do ACF2 shops use for Teradata batch security? Many thanks for any assistance! Ronan McGuirk AIB Bank
| ||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||
Copyright 2016 - All Rights Reserved | ||||||||||||||||||||||||||||||||||||||||||||||||
Last Modified: 15 Jun 2023 | ||||||||||||||||||||||||||||||||||||||||||||||||