|
We currently use Tivoli Identity Manager to manage iSeries, mainframe and Active directory profiles and we have always used QPWDLVL=0. My understanding is that Tivoli lets you determine and define which password rules to enforce, so you *could* enforce a "character in the first position of the password" rule. We've been on ITIM for two or three years now, according to the ITIM web logon we're at Tivoli Identity Manager 4.4.3 Build 4886. The biggest issue that we ran into on the iSeries side was that we changed the sync job to run every 10 seconds rather than the default of every 60 seconds to speed up the password synchronization. People were changing their password at the Windows startup and then getting their NetServer profiles disabled when mapping drives. Regards, Scott Ingvaldson iSeries System Administrator GuideOne Insurance Group -----Original Message----- date: Fri, 4 Aug 2006 15:27:54 -0400 from: "Harvell, Joel" <jbharvell@xxxxxxxxxxxx> subject: Changing from Password Level 0 to password Level 2 We are in the process of installing TIM - Tivoli Identity Manager here at our facility. The TIM software will manage passwords for The AS400, mainframe, Active directory, & lotus notes. Our AS400s are currently at Password level 0. (system value - QPWDLVL) Password level 0 will only allow a character in the first position of the password field. As part of the TIM install we have a need to have a numeric value in the 1st position of the password field. I read in the help on the system value QPWDLVL that a value of 2 or 3 will allow a numeric value in the 1st position. My question is what is the impact of changing our QPWDLVL value from 0 to 2?? Has anyone else implemented the Tivoli Identity Manager in their shop? Has anyone changed from 0 to 2 or 3 on QPWDLVL?? Thanks Joel B. Harvell Food Lion, LLC DISCLAIMER: This message and accompanying documents are covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, and contains information intended for the specified individual(s) only. This information is confidential. If you are not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, copying, or the taking of any action based on the contents of this information is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.