Seems like the tick box that says if users are notified or not shouldn't be
there then in Open Source, since it seems to apply only to the openUC
plugins. Does a Jira need to be created to remove it so it doesn't create
further confusion?
The simple solution for the passwords it seems is to just import them during
user creation, so that what is there is known in advance, and the
administrator doesn't have to go in and change each and every one.
I believe the options provided in the Jira still apply and can be a good
resolution.
From: sipx-users-***@list.sipfoundry.org
[mailto:sipx-users-***@list.sipfoundry.org] On Behalf Of Mircea Carasel
Sent: Wednesday, July 18, 2012 2:29 PM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] 4.6 Passwords
On Wed, Jul 18, 2012 at 11:26 PM, Todd Hodgen <***@frontier.com> wrote:
Have you seen that work. There is an option at the bottom with a tick mark,
with the following below it - Flag that informs if the user has been
notified of his system account creation.
I created two new users, both with a known working email address with the
system, one with the tick marked, the other not marked. I did not received
any email notifications.
If that is the intent of that tick mark, then I believe it needs to be
reworded to something like - "Notify New user of Account Creation" or
something similar.
Problems I see with this - has there been a method created that allows for
mass importing of users, and marking that tick mark at the same time?
George is right, OpenUc automatically sends emails when user gets created,
and the Notified checkbox automatically gets checked. This applies for mass
import of users, they will receive emails (if email address is also
specified)
In open-source, no email gets sent - the administrator should manually send
email or somehow inform the user about account creation
Mircea
I agree, making passwords that default, or the same is a security risk for
individual voicemails, but if they are forced to change on the first entry,
then I believe you have mitigated that risk. It's been a standard practice
in the industry to have a default password on voicemail system, so I believe
most are prepared for it. The other option is to leave it empty until it
is created, as it was in the past.
If notification is sent out, that is great. But if no notification, and a
random password, it just doesn't make a lot of sense.
From: sipx-users-***@list.sipfoundry.org
[mailto:sipx-users-***@list.sipfoundry.org] On Behalf Of Tony Graziano
Sent: Wednesday, July 18, 2012 12:35 PM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] 4.6 Passwords
I think the system can email the user their relevant passwords upon account
creation...
On Jul 18, 2012 3:14 PM, "Kurt Albershardt" <***@nv.net> wrote:
On Jul 18, 2012, at 1:15 , Todd Hodgen wrote:
Just for a point of discussion, setting these two password fields to random
numbers doesn't seem to provide any benefit to the administrator. I'm
assuming these are required to be there rather than a blank space. It
would be very beneficial to the administrator if something useable was put
into that field, even if they were all the same. For example - maybe a
specific number such as 5 + extension number. Or set them all to 1234 or
something similar. This way, the end user can be instructed on what is
there, and how to change it, rather than the administrator having to change
all of them to something useable.
With a random number, the end user can't log into voicemail or the GUI to
change it until after the administrator makes a change since it is random
and hidden.
Is there a "require password change on next login" option for the web portal
and voicemail? If a default passwords is populated, it should select this
option by default as well.
_______________________________________________
sipx-users mailing list
sipx-***@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/
LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: ***@voice.myitdepartment.net
Helpdesk Customers: http://myhelp.myitdepartment.net
Blog: http://blog.myitdepartment.net