Article ID: 49282


Updated On:


CA Cleanup CA Datacom CA DATACOM - AD CA CIS CA Common Services for z/OS CA 90s Services CA Database Management Solutions for DB2 for z/OS CA Common Product Services Component CA Common Services CA Datacom/AD CA ecoMeter Server Component FOC CA Easytrieve Report Generator for Common Services CA Infocai Maintenance CA IPC Unicenter CA-JCLCheck Common Component CA Mainframe VM Product Manager CA Chorus Software Manager CA On Demand Portal CA Service Desk Manager - Unified Self Service CA PAM Client for Linux for zSeries CA Mainframe Connector for Linux on System z CA Graphical Management Interface CA Web Administrator for Top Secret CA CA- Xpertware CA Top Secret CA Top Secret - LDAP CA Top Secret - VSE



With 2 CA Top Secret systems not sharing the security file, but using CPF to keep the security files in sync, if an ACID has the NOPWCHG attribure on 1 system but not on the other system, and that ACID changes the password at signon time on the system where it does not have the NOPWCHG attribute, the password change is propagated to the system where the ACID has NOPWCHG. Why?


This is functioning as intended. When the user changes the password on the system where NOPWCHG is not on the ACID and it propagates to the prod system where NOPWCHG is on the acid, the change on the receiving system is done as a command, not a signon. The NOPWCHG attribute only prevents ACIDs from changing passwords at signon or initiation.


Component: AWAGNT