So,

Would it make sense to run it on a sub as well since the DB replicates within 
the cluster? Just a thought.

I apologize for any typo's!
Sent from my iPhone

> On Jul 6, 2015, at 9:28 AM, Ryan Huff <[email protected]> wrote:
> 
> My suspicion is it has to do with controlling the number of queries being 
> issued and from where or perhaps and more specifically,  tracking the 
> failover itself. 
> 
> Once the failover occurred, the identity of the cucm-side ldap sync would 
> change and AD servers might not handle that gracefully. I don't see why not 
> but in a trusted-cert/LDAPS scenario it might have issues?
> 
> Still seems like there could be a stateful token or something that could be 
> passed around to whatever the active ldap sync node happens to be.
> 
> Thanks,
> 
> Ryan
> 
> 
> 
> -------- Original Message --------
> From: Lelio Fulgenzi <[email protected]>
> Sent: Monday, July 6, 2015 09:16 AM
> To: [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]> 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]
>> https://puck.nether.net/mailman/listinfo/cisco-voip
> _______________________________________________
> cisco-voip mailing list
> [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