UC Software Version 5.4.0.10182 Updater Version 5.6.0.14237
We appear to be encountering an issue, where when a normally BToE user, changes their password while not BToE the phone continues to attempt to authenticate to Exchange, with authentication now failing the account locks out in AD.
Is this expected behavior? Rather than continuing to attempt authentication it would be preferable to hold the attempts until the credentials had been updated.
James
This is one of the issues that prevent us from moving away from PIN auth.
I would suggest contacting your reseller and subbmitting a feature request.
I guesss I could disable the Exchange calendar. (feature.exchangeCalendar.enabled=0)
I'm hesitant as the users that like the intergration, really like.
Today we think we've see the lockout behaviour with a user that hadn't changed their password, but hadn't been 'better together' in a while.
I've emailed my Polycom SE but nothing back yet. :(
James
Hello James,
can you contact me with your details and who you dealing with on the Polycom end?
Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.
Best Regards
Steffen Baier
Polycom Global Services
Hello James,
any luck with providing me with these details ?
Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.
Best Regards
Steffen Baier
Polycom Global Services
Sent in a private message.
This issue seems to have reappeared for some of my users in 5.4.4.2473 with BToE 3.3.0
Too soon to say how widespread it'll be.
I know I'm a release behind, but I've had a look through the notes for 5.4.4 E (5.4.4.3041) and there's nothing on this issue.
As side note can the build ID be included in the zip file name and / or in the relase notes on the title page? It's great that it' on page 11 but more prominent placement would be better.
Thanks,
James
James,
We are seeing this same issue. Did you ever find a resolution?