Guest

Preview Tool

Cisco Bug: CSCvs34835 - Jabber in Team Messaging mode fails to register to Phone Services

Last Modified

Sep 28, 2020

Products (1)

  • Cisco Jabber for Windows

Known Affected Releases

12.8(0)

Description (partial)

Symptom:
Phone Services fails to authenticate and register.

The embedded browser is currently not supported for Jabber in Team Messaging mode which will affect the authentication flow when SSO or Oauth with Refresh token are enabled.

Conditions:
Jabber with Teams messaging mode is enabled

One of the following scenarios:
Webex is non-SSO, CUCM/EXP is SSO or OAuth.
Webex is SSO, CUCM/EXP is OAuth with refresh token without SSO.
Webex and CUCM/EXP have different IDPs


Jabber sends the following query to check SSO/Oauth configuration - https://<expFQDN>:8443/<base64encoded edge domain>/get_edge_sso?Username=<user> and receives the following XML:

<?xml version='1.0' encoding='UTF-8'?>
<SSOResult version="1.0"><Response><SingleSignOn><Status enabled="false"/><Token reuse="true"/></SingleSignOn></Response></SSOResult>
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)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.