hopefully when you upgrade to cm6, you can take advantage of the ldap directory integration to provide a single sign-on experience. This should be a welcomed feature by the user base, granted not every is positioned with a centralized directory for ccm to sync with.<br>
<br>If you can't do dirsync, then I would suspect you could use BAT to bulk update the password and pins if you are (rightfully so) concerned about security. Setting them to the last four of social, or month/year of birthday, etc.<br>
<br><div class="gmail_quote">On Feb 13, 2008 10:04 PM, Matthew Saskin <<a href="mailto:matt@saskin.net">matt@saskin.net</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I agree it's not ideal. From a practical standpoint, my guess would be<br>that passwords/PINs were previously stored using a one-way hash (why the<br>hashed ones couldn't move over and use the same hash with CM6 I don't know).<br>
<br>Perhaps Wes can enlighten us a bit. I agree it would be interesting to<br>hear the particular reasons for going this route...<br><br>-matt<br><div><div></div><div class="Wj3C7c"><br>Lelio Fulgenzi wrote:<br>> I can appreciate GUI changes. I'm always happy to see things change<br>
> when they make things easier to use.<br>><br>> But what I'm concerned with is the fact that they don't think it's<br>> necessary to port userIDs and passwords over.<br>><br>> Can you imagine having to tell thousands of users that you have to<br>
> reset your password? What about security risks? I don't know the<br>> details but if it sets everyone's password to a default password and<br>> you tell everyone this, that opens up some exposures, don't you think?<br>
><br>> I might not even an export/import utility?<br>><br>><br>> --------------------------------------------------------------------------------<br>><br>> Lelio Fulgenzi, B.A.<br>> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>
> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>> "Life expectancy would grow by leaps and bounds if green vegetables<br>> smelled as good as bacon."<br>
> Doug Larson<br>><br>><br>> ----- Original Message ----- From: "Matthew Saskin" <<a href="mailto:matt@saskin.net">matt@saskin.net</a>><br>> To: "STEVEN CASPER" <<a href="mailto:SCASPER@mtb.com">SCASPER@mtb.com</a>><br>
> Cc: "Cisco Voyp List" <<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>>; "Lelio Fulgenzi"<br>> <<a href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a>><br>
> Sent: Wednesday, February 13, 2008 9:30 PM<br>> Subject: Re: [cisco-voip] userID/password/PINs lost during migration<br>> from 4.x to 6.x<br>><br>><br>>> ccmuser UI is completely different than before ;)<br>
>><br>>> STEVEN CASPER wrote:<br>>>> Yes I do... our users are going to love that. I also read about the<br>>>> PAB and Fast Dial access options that change. Why change basic user<br>>>> interface functionality? Is there anything else that changes from<br>
>>> user perspective that is not advertised and is going to cause me<br>>>> grief? How about CCM user?<br>>>><br>>>> >>> "Lelio Fulgenzi" <<a href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a>> 2/13/2008 3:27 PM >>><br>
>>> Anyone else have some concern that in the migration from 4.x to 6.x<br>>>> you will lose all passwords and PINs?<br>>>> Essentially, you have to set them to some default password and then<br>
>>> have everyone go back in and change them.<br>>>> Lelio<br>>>> --------------------------------------------------------------------------------<br>>>><br>>>> Lelio Fulgenzi, B.A.<br>
>>> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>>>> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>
>>> "Buffalo buffalo Buffalo buffalo buffalo buffalo Buffalo buffalo." WJR<br>>>><br>>>> ************************************<br>>>> This email may contain privileged and/or confidential information<br>
>>> that is intended solely for the use of the addressee. If you are not<br>>>> the intended recipient or entity, you are strictly prohibited from<br>>>> disclosing, copying, distributing or using any of the information<br>
>>> contained in the transmission. If you received this communication in<br>>>> error, please contact the sender immediately and destroy the<br>>>> material in its entirety, whether electronic or hard copy. This<br>
>>> communication may contain nonpublic personal information about<br>>>> consumers subject to the restrictions of the Gramm-Leach-Bliley Act<br>>>> and the Sarbanes-Oxley Act. You may not directly or indirectly reuse<br>
>>> or disclose such information for any purpose other than to provide<br>>>> the services for which you are receiving the information.<br>>>> There are risks associated with the use of electronic transmission.<br>
>>> The sender of this information does not control the method of<br>>>> transmittal or service providers and assumes no duty or obligation<br>>>> for the security, receipt, or third party interception of this<br>
>>> transmission.<br>>>> ************************************<br>>>><br>>>> ------------------------------------------------------------------------<br>>>><br>>>><br>>>> _______________________________________________<br>
>>> cisco-voip mailing list<br>>>> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>>>> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
>>><br>>><br>>><br>><br><br>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</div></div></blockquote></div><br>