In my opinion - there are several things required - a) How about defaulting it on all new users, so it requires they reset the password after first access.
b) How about a tickmark that allows Administrator to force a change on a particular user c) How about a screen that list groups and allows you to force a group to change - allows for a group change if a breach is suspected d) How about a screen the admin can pull up and just add a tick next to multiple users he/she wants to have change their voicemail password. e) In general, I find that people don't change the default pin that we give to them on setup, which allows for anyone to list to the voicemails of others. From: [email protected] [mailto:[email protected]] On Behalf Of barisyanar Sent: Monday, February 13, 2012 3:50 PM To: sipXecs developer discussions Subject: Re: [sipx-dev] XX-9121 Voicemail Security - Force users to change PIN on 1st Login Hello all, I implemented a functionality around the new setting voicemail/security/force-pin-change. Placed a checkbox in user's "Unified Messaging" page, under a "Security" title which is shown as an advanced setting to the admin. However implementation for multiple users occured to be a bit problematic.(in case of a security breach etc.) I had started with providing this setting as a "User Group" "Security" option which turned out to be useless, since the setting for the user could not be altered from the group if it was set before from the user. Then I decided to implement configuration of multiple users for this setting as an action as "Add to Group/Remove from Group" in "Users Panel"s "action selection box". Multiple configuration would only cover the users selected in a page. This needed an execution of a batch operation for efficiency obviously. But I found out that "loading" of users in a loop is needed in order to publish the operations. Moreover users' "value storage" should be initialized first, in order to save the new setting to the database. I concluded that loading and saving users one by one would consume the same process power and memory as above implementation . I would really appreciate any ideas on this subject.
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
