All of our customer accounts (170,000) that are populated from LDAP (and authenticate to LDAP) get this checkbox selected as part of the integration that creates their CTM:People and User records. The 300 manually created and managed support staff accounts with local passwords are left subject to the OOTB password management rules. It was not that hard to separate the two types of users in our case, and they have been coexisting with no apparent problems. One caution if you modify any of the password management workflow - if you ever apply any patch to the AR Server using the installer, it will restore the original OOTB version of the password management workflow.
Christopher Strauss, Ph.D. Call Tracking Administration Manager University of North Texas Computing & IT Center http://itsm.unt.edu/ > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[EMAIL PROTECTED] On Behalf Of Grooms, Frederick W > Sent: Wednesday, October 29, 2008 9:10 AM > To: [email protected] > Subject: Re: Who has done any password management while using AREA LDAP > Authentication > > On 7.1 there is the "Disable Password Management For This User" > checkbox > > All you would have to do is to add code to set that field automatically > if the password is null > > Fred > > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[EMAIL PROTECTED] On Behalf Of David Durling > Sent: Wednesday, October 29, 2008 8:49 AM > To: [email protected] > Subject: Re: Who has done any password management while using AREA LDAP > Authentication > > I haven't used Remedy's password management, but Roger's suggestion > sounds good if Remedy will let you evaluate the password field contents > in a qualification. I don't think it will let you directly do that, > though. > > If that's true, how about a naming convention on the utility accounts > that you could search against (i.e., util-1, util-2, etc.), or perhaps > even adding an (admittedly unsupported) selection field on the User > form > to mark the accounts you want to exclude. > > David D. > > > Review the OOTB workflow and determine if you can add a qualification > > where password is not null should work. > > > > > > > > -----Original Message----- > > From: Danaceau, Chris <[EMAIL PROTECTED]> > > To: [EMAIL PROTECTED] > > Sent: Wed, 29 Oct 2008 9:04 am > > Subject: Who has done any password management while > > using AREA LDAP Authentication > > > > ** ITSM 7, ARS 7.1 > > > > > > > > Our issue is that while our LDAP password rules are good, we have > > some accounts solely in Remedy (utility accounts) for which we need > > to enforce password rules. The password Management function does > > not look like an option. We'd need to keep it disabled for the LDAP > > folks (99%) which would be a logistical nightmare. I'm leaning > > towards disabling the password change abilities for all users except > > contact people admin. I'm on a short deadline to come up with a > > solution, and the volume of passwords we would have to manage would > > be minimal. > > > > -- > David Durling 706-542-0223 > Enterprise IT Services [EMAIL PROTECTED] > University of Georgia > > _______________________________________________________________________ > ________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
