topic Hi, in Collaboration Applications

Jabber 11.1 - unable to login with user different from Windows Session

Kevin SAS — Mon, 18 Mar 2019 01:02:41 GMT

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

I think this may be related

bwalsh — Tue, 19 Apr 2016 00:28:19 GMT

I think this may be related to the UPN feature that later versions of Jabber introduced..

Try this:

1. Uninstall Jabber
2. Delete all cache directories after uninstallation

a. %AppData%\Local\Cisco\Unified Communications\Jabber
b. %AppData%\Roaming\Cisco\Unified Communications\Jabber
c. \Program Files (x86)\Cisco Systems\Cisco Jabber
d. \ProgramData\Cisco Systems\Cisco Jabber
3. Reboot
4. Install Jabber by using this command from command prompt (you’ll need to run command prompt as admin)
a. msiexec.exe /i CiscoJabberSetup.msi /quiet CLEAR=1 UPN_DISCOVERY_ENABLED=false

Attempt the login process where User B is logging into Jabber from User A’s workstation that is already authenticated to the domain.

Hi,

Kevin SAS — Tue, 19 Apr 2016 10:39:14 GMT

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