cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2825
Views
5
Helpful
8
Replies

Question about Jabber 11.9 sign-in

mcaldogne
Level 3
Level 3

Hi!

We have noticed that since Jabber 11.9 (Windows and Android),some users who have changed the LDAP password are logged in automatically but get no connection to CUCM and CUPS.

Could it have something to do with the new Fast Sign-in feature? If yes could I set "STARTUP_AUTHENTICATION_REQUIRED" to true, so that the user will be asked for  the new password in Jabber if the Windows password has been changed?

 

Any help would be greatly appreciated.

 

Thanks

Mirko

8 Replies 8

Jonathan Schulenberg
Hall of Fame
Hall of Fame
That isn’t the correct solution. That setting was created for customers where the SecOps teams have gone overboard and want to force the user to re-enter their password all the freaking time.

Look at the Service Profile on CUCM. Are the Phone Service and Voicemail services to reuse the sign-in credentials? If not then it isn’t working because Jabber is expecting those users to open Jabber preferences > Accounts and update their password per-Service. Change those settings, force a config refresh on the client, then quit/relaunch it.

Hi Jonathan,

Thanks for your help.

 

Under Service Profile on CUCM, for the system default Service Profile there are no Voicemail or Conferencing Profile, only Directory, IM and Presence and CTI.

 

How can I set the Service Profile in order to ask to user to insert the new password while signin-in?

With Jabber 11.5 the user became a warning that the password had changed and forced you to type the right password.

Thanks

Mirko

Finally, we've tested with Jabber 11.9 changing the Password and after that restarting the PC.

  1. Jabber start automatically and cannot connect immediatly to CUCM/IMP, but the user become a message in order to enter the new password:jabber1.jpg
  2. the user click on update and come into the account options:jabber2.jpg
  3. After typing the new password click on OK the jabber can connect to CUCM/IMP again:jabber3.jpg

Conclusion: compared to Jabber 11.5, the user can now start Jabber with the old password, than he will be warned that the password has changed. It works, but now the user has to type the password two times, first for IMP and second CUCM.

 

 

Hi mcaldogne,

 

we face the same issue. I do not like this procedure. Did you find a way, that the user do not have to enter manually the password for these services?

 

with kind regards,

I'm also having this issue. Did anyone find the fix?

Hi kely,

 

I'll open a tac today. Didn't find any solution for this.

 

with kind regards,
Andreas

Hi Kely,

 

I've got answer from TAC.

 

the new fast login feature which was introduced with 11.9 cause that the user has to enter the credential for the telephony and IM&Presence service.

So I've disabled the fastlogin feature and the password cache on the mobile devices with following paramters in the jabber config.xml.

 

  • <STARTUP_AUTHENTICATION_REQUIRED>true</STARTUP_AUTHENTICATION_REQUIRED>
  • <CachePasswordMobile>false</CachePasswordMobile>

It works fine for our needs.

 

Also TAC mentioned that there is a enhancement defect.

CSCvg56521 Enhancement: J4W-No notification or re-signing after password expired and changed in LDAP

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvg56521/?rfs=iqvred

 

with kind regards,
Andreas

 

** Internal Email **
Thanks for the update.
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: