CUPS client PW sync

Unanswered Question
Dec 19th, 2008
User Badges:


I've a cucmbe6.1(2) attached to a cups 6.0 server. Since cucmbe does not support ldap, we've a local user database. all users are cups enabled and presence works fine. If a user changes his password on cucmbe, the new password is not being updated or synced on cups client!

Any suggestions?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
billriley19795 Sun, 12/21/2008 - 11:54
User Badges:

That is the way it works. Even in CUPS 7.0 you still have that problem. Hopefully it will work like OCS sometime and use the windows logon account.

bjoern.kirchhof Mon, 12/22/2008 - 06:21
User Badges:

so, if this "normal behaviour". which service has so be restarted in order to sync pw?

billriley19795 Mon, 12/22/2008 - 06:32
User Badges:

I don't think CUPS will sync the password at the client level. Everytime the password changes they have to change it in the client. You can sync the passwords from Call Manager to your AD domain. When the users changes their network password their call manager password will change and stay in sync but it will not change at the client level as far as I know.

bjoern.kirchhof Fri, 01/02/2009 - 10:34
User Badges:

misunderstoood. not the changing of the clients password is the question.

once more I've am business edition version with NO DLAP integration, since this is not possible!

So, after changing the user pw on ccm side, the cups SERVER is not aware of the new password!

The pw is being synced after cups SERVER reboot!

billriley19795 Fri, 01/02/2009 - 10:41
User Badges:

So the problem is that you change the password on the CUCMBE server and the CUPS server does not get the new password so when you try to log into the CUPC client it fails? That sounds like some type of bug. I have not had that problem.

htluo Fri, 01/02/2009 - 11:20
User Badges:
  • Red, 2250 points or more

This is called "change notification failed". You may restart SyncAgent to work around that.

The root cause is clustermanager not able to set up a TLS connection between CUPS and CUCM. We need ClusterManager logs to troubleshoot. Possible cause could be:

#1 IP address/hostname was changed at some point.

#2 Secret password was changed at some point.

My blog:


This Discussion