Cisco Bug: CSCuo86623 - Impossible to Sign-in as different user when ServiceDomain is unknown
Feb 07, 2017
- Cisco Jabber for Windows
Known Affected Releases
Symptom: After performing a "sign-in as different user", all authentication attempts will fail. Conditions: 1. Administrators configured the ServiceDomain along with the DNS SRV records under a domain which is not regularly used by its end-users. 2. Jabber is deployed using a bootstrap file which specifies the ServiceDomain and CUP deployment type. This works fine for the first end-user to sign on after the initial installation. 3. A different end-user attempts to sign-on to Jabber from the same PC. Jabber will force a "sign-in as different user" and force the new end-user to enter in their username in the "email@example.com" format. 4. The new end-user attempt to sign-in to Jabber using the domain associated with their E-Mail address, rather than the domain which the Administrators configured for ServiceDomain. 5. Jabber will attempt Service Discovery on the domain entered for the end-users username, rather than the domain specified in the ServiceDomain from the bootstrap file, and authentication will fail.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases