Hi all,
We have a system of ~3,000 staff users, and ~3,000 "room" phone, all which have been configured with the same password on creation in the AVAYA Aura VoIP phone system. In order to make our network more secure we would like to go towards a password per user policy (doesn't necessarily have to be unique) but not to touch the "room" phones at this point in time.
We have been advised that using the REST API to batch-change users' passwords still requires users input to activate their password before it gets updated, and unfortunately, a large majority of our user base is likely to ignore emails regarding phone system passwords (which would cause the password not to get updated from our understanding.)
We also have been advised that there is a password aging policy that we could turn on but it would apply to all accounts on the system, and there would be no way to exclude the "room" phones from this.
Our current solution to solve this problem is to
Is there a better way to go about forcing password changes for a sub-sect of users?
We have a system of ~3,000 staff users, and ~3,000 "room" phone, all which have been configured with the same password on creation in the AVAYA Aura VoIP phone system. In order to make our network more secure we would like to go towards a password per user policy (doesn't necessarily have to be unique) but not to touch the "room" phones at this point in time.
We have been advised that using the REST API to batch-change users' passwords still requires users input to activate their password before it gets updated, and unfortunately, a large majority of our user base is likely to ignore emails regarding phone system passwords (which would cause the password not to get updated from our understanding.)
We also have been advised that there is a password aging policy that we could turn on but it would apply to all accounts on the system, and there would be no way to exclude the "room" phones from this.
Our current solution to solve this problem is to
1) Manually export all users from SMGR, update the passwords to a random user password and re-upload of all users and passwords through SMGR (this would force the password change, but users would not have their new password available to them).
2) We would then call the REST API batch password change using a set of random passwords which would notify users of the new password, and they could activate their password and re-sign into their desk phone if they have one.
Is there a better way to go about forcing password changes for a sub-sect of users?
