Guest

Cisco Unified Contact Center Express

Field Notice: FN - 63626 - SocialMiner Twitter Account Does Not Authorize

Field Notice: FN - 63626 - SocialMiner Twitter Account Does Not Authorize

March 13, 2013


NOTICE:

THIS FIELD NOTICE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTY OF MERCHANTABILITY. YOUR USE OF THE INFORMATION ON THE FIELD NOTICE OR MATERIALS LINKED FROM THE FIELD NOTICE IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS FIELD NOTICE AT ANY TIME.

Revision History

Revision Date Comment
1.0
13-Mar-2013
Initial Public Release

Products Affected

Products Affected Comments
SocialMiner
SocialMiner Release 9.0(1) COP-3 and earlier. 

Problem Description

SocialMiner Twitter account does not authorize.

Background

Customers are not able to add or reauthorize Twitter accounts on SocialMiner with the third Cisco Options Package (COP). The oAuth protocol fails because Twitter changed its application programming interface (API) URLs.

Problem Symptoms

The issue impact is high. Customers are unable to add a Twitter account.

In the Cisco Configuration Professional (CCP) API logs, you see these exceptions:

0000000230: 172.22.23.135: Feb 25 2013 10:22:39.255 -0600: %CCBU_________CCPAPI-3-REST_API_EXCEPTION: %[exception=com.cisco.ccbu.ccp.feeds.exception.FeedOAuthException: oauth.signpost.exception.OAuthCommunicationException: Communication with the service provider failed: Service provider responded in error: 301 (Moved Permanently)][message_string=feed]: The REST API has caught an exception
0000000231: 172.22.23.135: Feb 25 2013 10:22:39.255 -0600: %CCBU_________CCPAPI-3-EXCEPTION_INFO: %[build_date=Dec 31, 1969 6:00 PM][build_type=rel][exception=com.cisco.ccbu.ccp.feeds.exception.FeedOAuthException: oauth.signpost.exception.OAuthCommunicationException: Communication with the service provider failed: Service provider responded in error: 301 (Moved Permanently)

Workaround/Solution

If you have SocialMiner Release 8.5(5), you must upgrade to 
Release 9.0(1). Then apply the COP3 file, and follow the workaround instructions. 

If you have SocialMiner Release 9.0(1) with COP1 file or COP2 file applied, then you must upgrade to COP3, and follow the workaround instructions. 

Download the SocialMiner Release 9.0(1) COP3 software.

Twitter has modified their authentication URLs. 

The URLs used to authenticate with Twitter can be modified to match Twitter's updated URLs. Follow these steps to update: 

  1. Log into VOS CLI as admin.
  2. Enter run sql INSERT INTO mmca_propertydef (propertydefid, propertyname, description, defaultvalue, subsystype, ouid) VALUES (88020, "twitterUrlOauthAuthorize", "Twitter oAuth Authorize URL", "https://api.twitter.com/oauth/authorize", 0, 2).
  3. Enter run sql INSERT INTO mmca_propertydef (propertydefid, propertyname, description, defaultvalue, subsystype, ouid) VALUES (88021, "twitterUrlOauthAccessToken", "Twitter oAuth Access Token URL", "https://api.twitter.com/oauth/access_token", 0, 2).
  4. Enter run sql INSERT INTO mmca_propertydef (propertydefid, propertyname, description, defaultvalue, subsystype, ouid) VALUES (88022, "twitterUrlOauthRequestToken", "Twitter oAuth Request Token URL", "https://api.twitter.com/oauth/request_token", 0, 2).
  5. Enter the command utils service restart Cisco Tomcat.

DDTS

To follow the bug ID link below and see detailed bug information, you must be a registered customer and you must be logged in.

DDTS Description
CSCue76034 (registered customers only) SocialMiner oAuth requests to Twitter fails due to REST API change.

For More Information

If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:

Receive Email Notification For New Field Notices

Cisco Notification Service — Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.