Currently, the 'Disabled' flag is for informational purposes only and does not have an effect on the actual user or login process. So yes, you'd need to use workflow were you to want to do something based on the status of that field.
There have been suggestions that the system should have an indicator on the technical status (rather than informational status) of a user that has an effect on whether they can log in or not and this is being considered for a future release. This dovetails into broader requests to enable, for example, the disabling of a user for a time period (e.g. while they're on holiday) and re-enabling them upon their return. -David J. Easter Manager of Product Management, Remedy Platform BMC Software, Inc. The opinions, statements, and/or suggested courses of action expressed in this E-mail do not necessarily reflect those of BMC Software, Inc. My voluntary participation in this forum is not intended to convey a role as a spokesperson, liaison or public relations representative for BMC Software, Inc. From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Jack Boespflug Sent: Tuesday, January 25, 2011 08:34 AM To: [email protected] Subject: Re: Force Password Change On Login ** Thanks for the info. That brings up another question then, what indicates that the User record is disabled? Is it the Status field set to "Disabled", or some other field that I am not aware of? When the Status value is set to Disabled, the user can still login. Do I need to change my application code to also check this field? John Baker also suggested there is a field called "User account locked". I am not seeing this field on the User form. Does it exist somewhere else? I will probably need to direct these questions to BMC, but wanted to see if others have run into this. Thanks again for any info you have. Jack Boespflug Product Development Kinetic Data, Inc. "Building a Better Service Experience" Recipient of : WWRUG10 Best Customer Service/Support Award WWRUG09 Innovator of the Year Award On Tue, Jan 25, 2011 at 8:50 AM, LJ LongWing <[email protected]<mailto:[email protected]>> wrote: ** Jack, Unfortunately I do not believe that the pw management stuff is a server thing, I think the client and mid-tier were programmed to look at that information and take action...that being said, you would need to write your API program to do the same. From: Action Request System discussion list(ARSList) [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Jack Boespflug Sent: Monday, January 24, 2011 4:22 PM To: [email protected]<mailto:[email protected]> Subject: Force Password Change On Login ** AR Server version: 7.06.03 Build 001 Using the API, does the ARServerUser.login() method check if 'Force Password Change On Login' (field 124) is set before logging in the user, or is the program using the API responsible for checking that field? I didn't see anything mentioned in the API docs about changes to the login process, but the login method doesn't seem to care if this field is set or not, it logs the user in with the old password and allows the user to continue as if the old password is still valid. Thanks, Jack Boespflug Product Development Kinetic Data, Inc. "Building a Better Service Experience" Recipient of : WWRUG10 Best Customer Service/Support Award WWRUG09 Innovator of the Year Award _attend WWRUG11 www.wwrug.com<http://www.wwrug.com> ARSlist: "Where the Answers Are"_ _attend WWRUG11 www.wwrug.com<http://www.wwrug.com> ARSlist: "Where the Answers Are"_ _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
