CUPC ad athentication

Answered Question
May 1st, 2010

Hi all:


I've the following scenario:


win2003 ad --- ucm 7.0.1 --- cup 7.0.2


ucm is succsesfully integrated with ldap and with cup, everything is working from ucm ldap is full sycnh and also cupc works as expectec, I can search in ad also I see the presence of other phones etc


The problem i had is that when I set ldap authentication I can't log in to upc, is strange becouse from the ucm user weg page I can log with the new password that is set in ad schema, but from upc or cup user web page I can't log, seem to be a problem between cup and ad...


I'm not using ssl to authenticate


Any suggestion would be higly apreciate


Regards

Correct Answer by William Bell about 6 years 10 months ago

Right. Well, you at least need to restart the tomcat service. I feel like I am always restarting the tomcat service on CUPS (at least during a build-out)


Regards,

Bill

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Aaron Harrison Sat, 05/01/2010 - 05:31

Hi


Last time I recall switching UCM to AD when CUPS was already running, I believe I needed to restart the CUPS server before it would work correctly.


Regards


Aaron


Please rate helpful posts..

Correct Answer
William Bell Sat, 05/01/2010 - 05:48

Right. Well, you at least need to restart the tomcat service. I feel like I am always restarting the tomcat service on CUPS (at least during a build-out)


Regards,

Bill

htluo Sat, 05/01/2010 - 07:15

CUPC login was handled by the SOAP service on CUPS.


SOAP runs on HTTP (Tomcat).  Authentication was done by Tomcat.


Whenever you made changes to authentication (such as enable/disable LDAP authentication, change search context, integration password, etc.), you need to restart Tomcat.


You may do it from CUPS command line:


utils service restart Cisco Tomcat


Michael

http://htluo.blogspot.com

Actions

This Discussion