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"
