Preview Tool

Cisco Bug: CSCvv92961 - Jabber revokes Access token for all services when 401 Unauthorized received from Unity Connection

Last Modified

Oct 07, 2020

Products (1)

  • Cisco Jabber for Windows

Known Affected Releases

12.6(2) 12.6(3) 12.7(1) 12.8(1) 12.9(1)

Description (partial)

Cisco Jabber invalidates Access token when 401 Unauthorized received from Unity Connection (CUC). This is per design in the situations described below. 

Consider the following flow:
1. Jabber logs into UCM which is enabled for Refresh login flow and obtains an access token.
2. Jabber reaches out to CUC (as per Voicemail Profile in the Service Profile)
3. CUC rejects the request with 401 Unauthorized 

At this point, Jabber will invalidate the access token for all services (CUCM, IMP, CUC..). This is expacted behaviour.

-Cisco Jabber 12.6.2 and later
-CUCM and CUC both enabled for OAuth with Refresh login flow
-CUC meets one of these conditions:
a) User does not have any Unity Connection Account
b) User password on CUC is has expired or is about to expire
c) User has the "User Must Change at Next Sign-In' option checked
d) Latest OAuthz keys not synced to CUC
Bug details contain sensitive information and therefore require a 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.