McDewey

Table 18: System Administrator Security Token (SAST) Roles of CTL File SAST Roles in Tokenless CTL File SAST Roles in Token-based CTL File Cisco Unified Communications Manager Version ITLRecovery (Signer) CallManager Token 1 (Signer*) Token 2 ITLRecovery CallManager 12.0(1) CallManager (Signer) ITLRecovery Token 1 (Signer) Token 2 ITLRecovery CallManager 11.5(x) CallManager (Signer) ITLRecovery Token 1 (Signer) Token 2 10.5(2) CallManager (Signer) Token 1 (Signer) Token 2 10.5(1) (Not supported) CallManager (Signer) Token 1 (Signer) Token 2 10.0(1) (Not supported) Not applicable Token 1 (Signer) Token 2 9.1(2) SIP OAuth Mode SIP OAuth mode allows you to use OAuth refresh tokens for Cisco Jabber authentication in secure environments. Supporting OAuth on the Unified Communications Manager SIP line allows secure signalling and media without CAPF. OAuth token validation during SIP registration is completed when OAuth based authorization is enabled on Unified Communication Manager cluster and Cisco Jabber endpoints. OAuth support for SIP registrations is available for Cisco Jabber devices and certain Phone models. For more information on SIP OAuth, see Feature Configuration Guide for Cisco Unified Communications Manager. SIP OAuth Configuration Through CLI Using CLIs, you can configure the Cluster SIP OAuth mode. For more information on how to configure SIP OAuth mode on Cisco Unified Communication Manager, see Feature Configuration Guide for Cisco Unified Communications Manager, Release 14. Note Consider the following points: Security Guide for Cisco Unified Communications Manager, Release 15 and SUs 92 Basic System Security SIP OAuth Mode