04-18-2016 06:44 AM - edited 03-17-2019 06:02 PM
Hello guys,
I have a problem after amigration from CUCM 8.6 to 10.5 on my Jabber clients.
The problem is related to service domain discovery I think, but I am unable to find the root cause.
Before, in 8.6 I authenticate through CUP with this configuration in my jabber-config.xml :
<ServiceDiscoveryExcludedServices>WEBEX,CUCM</ServiceDiscoveryExcludedServices>
So, to follow best practices for version 9.X and later, I do this :
<ServiceDiscoveryExcludedServices>WEBEX</ServiceDiscoveryExcludedServices>
To allow jabber to discover CallManager Service profile through UDS records.
My problem:
- User A is logged on Windows Session
- User B login successfully on Jabber (freshly resetted) and retrieve correctly jabber-config then signout
- When user B try to login another time, Jabber replace his username by User A wich result in authentication failure (and locked account for user A -> funny )
I didn´t find anything(and I don´t know what to research) in the Jabber log, Jabber successfully discovers UDS then CUP records. In Wireshark traces, I can see successful request for UDS and CUPlogin.
Some points :
- I am sure that jabber-config.XML is correctly downloaded from jabber
- I am sure my DNS records are corrects
- I think this problem is liable to service domain discovery but don´t know how
So if someone has an idea, I will test.
Thanks !
Kevin
Solved! Go to Solution.
04-18-2016 05:28 PM
I think this may be related to the UPN feature that later versions of Jabber introduced..
Try this:
Attempt the login process where User B is logging into Jabber from User A’s workstation that is already authenticated to the domain.
04-18-2016 05:28 PM
I think this may be related to the UPN feature that later versions of Jabber introduced..
Try this:
Attempt the login process where User B is logging into Jabber from User A’s workstation that is already authenticated to the domain.
04-19-2016 03:39 AM
Hi,
Thank you for your precise response.
It was that. I already did some tests with
UPN_DISCOVERY_ENABLED=false
but I didn´t flush all files correctly. So now, it Works as atended.
Thank you very much !
Little question : do you know if it posible to do the same result with an option in jabber-config.XML ?
I red all availables options and it appears not. We are able to change servicesdomain and excludedservices, but no option to change UPN. Shame
Kevin
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: