FYI - Just ran a quick test in a lab environment - LDAP user authentication 
against a Subscriber node while the Publisher’s network adapter is 
disconnected. Works as expected. Also running CUCM 10.5 but this (DirSync 
Synchronization vs. Tomcat Security authentication) also applies going back to 
7.x as far as I recall.

Hope this helps

- Dan


From: cisco-voip [mailto:[email protected]] On Behalf Of 
Daniel Pagan
Sent: Monday, July 06, 2015 9:45 AM
To: Lelio Fulgenzi; [email protected]
Subject: Re: [cisco-voip] LDAP Authentication when CUCM publisher is down.

LDAP authentication is used by Tomcat and isn’t just restricted to the 
Publisher server - Subscriber nodes handle this as well. DirSync is specific to 
synchronization of LDAP attributes and only runs on the Pub, so synchronization 
would definitely be affected if the Publisher is offline. I suggest to check 
out the Tomcat Security logs off CUCM for more info on user authentication 
against LDAP and your source of failure.

So to answer your question, LDAP authentication should still work when the 
Publisher is offline.

For the UCCX agent concern, authentication of agents occur over AXL to CUCM, so 
if the AXL server is the Publisher, and that’s offline or experiencing issue w/ 
Tomcat during an authentication attempt by the UCCX agent, then I would imagine 
seeing a failure. AXL and Tomcat Security logs off the UCM side should shed 
some light on that problem

As for SSO, I checked w/ my teammate and, in his experience, SSO can be handled 
by Subscriber nodes assuming the metadata was imported to those servers - 
authentication occurs against the IdP and not CUCM so this seems logical to me 
as well.

Hope this helps.

- Dan


From: cisco-voip [mailto:[email protected]] On Behalf Of Lelio 
Fulgenzi
Sent: Monday, July 06, 2015 9:16 AM
To: [email protected]<mailto:[email protected]>
Subject: Re: [cisco-voip] LDAP Authentication when CUCM publisher is down.


This has been our experience as well. Glad you started this thread. It's seems 
like a huge single point of failure to me for such an integral part of the 
process. I suspect hunt group login would also be affected.

Sent from my iPhone

On Jul 6, 2015, at 5:02 AM, Matthew Collins 
<[email protected]<mailto:[email protected]>> wrote:
Hi All,

CUCM 10.5

Just trying to get some conformation, When LDAP Synchronization and 
authentication is enabled this is performed by the DirSync process that only 
runs on the CUCM Publisher. So If we lose the CUCM Publisher for whatever 
reason it would seem that the Authentication also fails due to the single point 
of failure of DirSync. Should LDAP authentication still work if the CUCM 
Publisher is still down.

So for LDAP users this would stop them signing in to Jabber clients and UCCX 
agents who are ldap’ed synced logging into the finesse webpages. Does anyone 
know is SSO is resilient on the CUCM publisher or would SSO still work in a 
Publisher outage.

Regards

Matthew Collins

_______________________________________________
cisco-voip mailing list
[email protected]<mailto:[email protected]>
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/cisco-voip

Reply via email to