000030394 - Illegal character entity error when deviceName contains emoji

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000030394
Applies ToRSA Product Set: Adaptive Authentication (OnPrem), RSA Mobile SDK
RSA Product/Service Type: Adaptive Authentication (OnPrem), RSA Mobile SDK
RSA Version/Condition:Adaptive Authentication (OnPrem) 7.1, RSA Mobile SDK 2.0.1
Platform: Any
IssueWhen deviceName collected from RSA Mobile SDK contains emoji, AA Server throws an error. This is due to emoji is not a valid XML character hence AA Server XML parser fails to parse XML from the SOAP request.

ResolutionThe issue can be addressed by applying either of the following workaround:
      1. By wrapping the JSON string collected from mobile SDK with CDATA(starts with <![CDATA[ and ends with ]]> ). For example:
  "HardwareID" : "3884048B-478A-494C-871B-1DEC029640C6",
  "TIMESTAMP" : "2014-05-02 03:29:07 +0000",
  "DeviceModel" : "iPhone",
  "Languages" : "en-GB",
  "DeviceSystemVersion" : "7.0.2",
  "DeviceName" : "Jason&#x2019;s iPhone&#xD83D;&#xDE22;&#xD83D;&#xDE22;&#xD83D;&#xDE13;&#xD83D;&#xDE13;&#xD83D;&#xDE29;&#xD83D;&#xDE29;",
  "GeoLocationInfo" : [
  "OS_ID" : "21B940EA-4AB5-40E4-A972-BB4DFF7E020D"

      2. By keeping only alphanumeric characters for deviceName
  1. Workaround mentioned above requires modification of RSA Mobile SDK’s JSON string(mobileSdkData) in the client(mobile application) side
  2. Currently there is no plan on fixing this issue in the future RSA Mobile SDK release. The issue is still persists with RSA Mobile SDK version 2.0.1